From: Peter Stephenson <pws@ifh.de>
To: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: call this a mark??
Date: Thu, 16 Jan 1997 17:41:06 +0100 [thread overview]
Message-ID: <199701161641.RAA29990@hydra.ifh.de> (raw)
I suppose this is just my ignorance, but I was amazed to discover just
now (playing with the history lines thing) that the `mark' in zle is
not a mark at all, just a character offset which is confused by
insertion and deletion. Shouldn't it be possible to do something
about this by adding code to spaceinline(), backkill/del(),
forekill/del() -- or are there hidden problems?
--
Peter Stephenson <pws@ifh.de> Tel: +49 33762 77366
WWW: http://www.ifh.de/~pws/ Fax: +49 33762 77413
Deutsches Elektronen-Synchrotron --- Institut fuer Hochenergiephysik Zeuthen
DESY-IfH, 15735 Zeuthen, Germany.
next reply other threads:[~1997-01-16 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-16 16:41 Peter Stephenson [this message]
1997-01-17 0:20 ` Zoltan Hidvegi
1997-01-17 1:56 ` Daniel Reish
1997-01-17 8:32 ` 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=199701161641.RAA29990@hydra.ifh.de \
--to=pws@ifh.de \
--cc=zsh-workers@math.gatech.edu \
/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).