From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: ZLE and handling of MARK
Date: Thu, 5 Oct 2000 10:18:13 +0200 (MET DST) [thread overview]
Message-ID: <200010050818.KAA12655@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Sat, 9 Sep 2000 20:14:15 +0000
Bart Schaefer wrote:
> If one sets the mark in zle and then delete characters to the left of it
> by assigning to a slice of $BUFFER in a user-defined widget, the mark
> remains in the same numeric position rather than the same logical position.
>
> If instead one deletes characters by using the builtin widgets, the mark
> stays in the same logical position (its numeric position changes as the
> line gets shorter). The two cases should be consistent, no?
Yes, but how? The only `secure' change I can see is to update the
position of the mark if it is in $RBUFFER and only $LBUFFER is
changed. Otherwise we would need some, probably complicated, code to
check how $(|L|R)BUFFER was changed (ok, for deletion/insertion of
characters or short strings from/to the end/beginning of L/RBUFFER
this seems doable).
> One other observation:
>
> If one sets the mark and then moves around in the history, the mark stays
> at the same numeric position in each recalled line, moving only if a line
> is too short for it to stay in that position AND some reference to the mark
> is made (such as invoking exchange-point-and-mark). I'm not sure whether
> such behavior makes sense or not ... and if it changes, some functions in
> Functions/Zle will have to change, too.
It's a bit like emacs' line-movement, isn't it?
(I always thought the mark should be either attached to a history line
so that exchange-p-a-m would toggle between lines, or it should be
per-line. Maybe.)
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-10-05 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-05 8:18 Sven Wischnowsky [this message]
2000-10-05 16:58 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2000-09-09 20:14 Bart Schaefer
2000-09-10 21:13 ` Peter Stephenson
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=200010050818.KAA12655@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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).