From: Kenichi Handa <handa@m17n.org>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: overlay property `after-string'
Date: Fri, 11 Apr 2003 13:53:07 +0900 (JST) [thread overview]
Message-ID: <200304110453.NAA18583@etlken.m17n.org> (raw)
In-Reply-To: <buollyhwsws.fsf@mcspd15.ucom.lsi.nec.co.jp> (message from Miles Bader on 11 Apr 2003 13:37:55 +0900)
I changed Subject:
In article <buollyhwsws.fsf@mcspd15.ucom.lsi.nec.co.jp>, Miles Bader <miles@lsi.nec.co.jp> writes:
> Kenichi Handa <handa@m17n.org> writes:
>> > How about using an overlay with an `after-string' property, located at
>> > the end of the minibuffer, for the minibuffer-message message itself?
>> > Then there's no modification/insertion at all...
>>
>> Unfortunately, the cursor is shown after that `after-string'
>> in that case.
> Oh yeah, that !@#*& problem -- I ran in the same thing when I was trying
> to do my `error messages don't obscure the users input' patch a long time
> ago.
> That behavior really should simply be fixed, it's stupid
> (but unfortunately, not entirely trivial to fix either).
I'm not sure that the current behaviour is a bug.
(let (overlay)
(insert "abc")
(setq overlay (make-overlay (- (point) 3) (point)))
(overlay-put overlay 'after-string "hello")
(sit-for 2)
(delete-overlay overlay))
In this case, it seems that the current behaviour is correct
(i.e. the cursor is shown after "hello").
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2003-04-11 4:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 1:44 Potential problem of minibuffer-message Kenichi Handa
2003-04-10 13:44 ` Stefan Monnier
2003-04-11 2:22 ` Kenichi Handa
2003-04-11 2:38 ` Miles Bader
2003-04-11 4:31 ` Kenichi Handa
2003-04-11 4:37 ` Miles Bader
2003-04-11 4:53 ` Kenichi Handa [this message]
2003-04-11 5:02 ` overlay property `after-string' Miles Bader
2003-04-11 6:30 ` Kenichi Handa
2003-04-13 11:23 ` Potential problem of minibuffer-message Richard Stallman
2003-04-10 22:47 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200304110453.NAA18583@etlken.m17n.org \
--to=handa@m17n.org \
--cc=monnier+gnu/emacs@rum.cs.yale.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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).