From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Behaviour of {beginning,end}-of-buffer-or-history
Date: Thu, 02 Jun 2011 07:25:53 -0700 [thread overview]
Message-ID: <110602072553.ZM15639@torch.brasslantern.com> (raw)
In-Reply-To: <4DE6FDA4.6060705@realraum.at>
On Jun 2, 5:04am, Bernhard Tittelbach wrote:
}
} > beginning-or-end-of-somewhere() {
} > local hno=$HISTNO
} > zle .${WIDGET:s/somewhere/line-hist/} "$@"
} > if (( HISTNO != hno )); then
} > zle .${WIDGET:s/somewhere/buffer-or-history/} "$@"
} > fi
} > }
} > zle -N beginning-of-somewhere beginning-or-end-of-somewhere
} > zle -N end-of-somewhere beginning-or-end-of-somewhere
} >
}
} Mhh, just when I got used to jumping to the beginning/end of a
} multi-line buffer with a double keypress of HOME/END ...
A quick test of [[ $LBUFFER[-1] = $'\n' ]] should fix that.
beginning-or-end-of-somewhere() {
local hno=$HISTNO
if [[ "${LBUFFER[-1]}" = $'\n' ]]
then
zle .${WIDGET:s/somewhere/buffer-or-history/} "$@"
else
zle .${WIDGET:s/somewhere/line-hist/} "$@"
if (( HISTNO != hno )); then
zle .${WIDGET:s/somewhere/buffer-or-history/} "$@"
fi
fi
}
zle -N beginning-of-somewhere beginning-or-end-of-somewhere
zle -N end-of-somewhere beginning-or-end-of-somewhere
next prev parent reply other threads:[~2011-06-02 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 19:57 Bernhard Tittelbach
2011-06-02 2:22 ` Bart Schaefer
2011-06-02 3:04 ` Bernhard Tittelbach
2011-06-02 14:25 ` Bart Schaefer [this message]
2011-06-02 16:02 ` Bernhard Tittelbach
-- strict thread matches above, loose matches on Subject: below --
2011-06-01 19:43 Bernhard Tittelbach
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=110602072553.ZM15639@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@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).