From: Rocky Bernstein <rockyb@rubyforge.org>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Bart Schaefer <schaefer@brasslantern.com>, Zsh Users <zsh-users@zsh.org>
Subject: Re: An example of writing a custom history file?
Date: Mon, 15 Dec 2014 22:58:05 -0500 [thread overview]
Message-ID: <CANCp2gZQXwm4E8qroza1mMtvcxtLwtY-_8SOwRA+ZWCEKEdriw@mail.gmail.com> (raw)
In-Reply-To: <CAHYJk3ThP=TFDRVGKZOZ9du9MjLJJcYAL-Yesb0Q4D8HPevsGQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
On Mon, Dec 15, 2014 at 1:22 PM, Mikael Magnusson <mikachu@gmail.com> wrote:
> On Mon, Dec 15, 2014 at 6:05 PM, Rocky Bernstein <rockyb@rubyforge.org>
> wrote:
> > Making the change suggested, adding 1000 doesn't change the behavior - no
> > file is written. Again, here is the entire 12-line program:
>
> Please don't top post.
>
> I was able to get your example to work as-is by adding -i to the
> hashbang line. None of the other suggestions in this thread made any
> difference.
>
Thanks - that worked. And as you report, none of the other suggestions did.
The following problem I can work around, but I mention because it is weird.
When I go back and add -i or --interactive to zshdb, the completion
menu comes in the line before rather than after, but what is more
troublesome is that the entered text after
the prompt isn't cleared.
So, for input:
zshdb<1> set hi<tab>
instead of:
highlight history
zshdb<1> set highight
I get:
zshdb<1> set hiset highlight
highlight history
Some more info which may be relevant.
I tried to reproduce this in that little 12 line program by adding the
relevant code that I am using:
completer() {
((2 == CURRENT)) && compadd -- fee fie foo
}
zle -C test_complete menu-expand-or-complete completer
bindkey '^i' test_complete
That works fine. It seems to have to do with the fact that in order to
make sure in zshdb that I have an interactive terminal I open a new one.
So I'm guessing that has something to do with the behavior above.
next prev parent reply other threads:[~2014-12-16 3:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 1:38 Rocky Bernstein
2014-12-15 2:53 ` Bart Schaefer
2014-12-15 7:09 ` Rocky Bernstein
2014-12-15 8:37 ` Bart Schaefer
2014-12-15 14:26 ` Rocky Bernstein
2014-12-15 16:14 ` Bart Schaefer
2014-12-15 17:05 ` Rocky Bernstein
2014-12-15 17:46 ` Peter Stephenson
2014-12-15 18:22 ` Mikael Magnusson
2014-12-16 3:58 ` Rocky Bernstein [this message]
2014-12-15 18:26 ` Bart Schaefer
2014-12-15 18:34 ` Mikael Magnusson
2014-12-16 11:36 ` Peter Stephenson
2014-12-16 5:57 ` Rocky Bernstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANCp2gZQXwm4E8qroza1mMtvcxtLwtY-_8SOwRA+ZWCEKEdriw@mail.gmail.com \
--to=rockyb@rubyforge.org \
--cc=mikachu@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).