unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21710@debbugs.gnu.org, ohwoeowho@gmail.com
Subject: bug#21710: 25.0.50; self-insert-command before a folded outline inserts after the outline
Date: Sun, 15 Aug 2021 20:12:10 +0200	[thread overview]
Message-ID: <87czqeinlx.fsf@gnus.org> (raw)
In-Reply-To: <8335raaa0x.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 15 Aug 2021 20:32:46 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> I get in Emacs 28 exactly what the OP describes.

[...]

>> On the other hand, I'm not sure quite what it's supposed to do if you
>> type after the dots.
>
> He was typing _before_ the dots.  He said "move to the end of foo".

Oh, before the dots...

OK, hide the sublevels and then hit "t" twice.  I get:

* foo...t|
* bar...

Unhiding:

* foot
some textt
* bar
some text

So I'm not getting the "bartt"?

> But isn't that expected, given the way outline-minor-mode uses the
> invisible property?

Probably, but it's not ... good?  I have a vague feeling the correct
pre-advance/post-advance (or whatever they're called) properties on the
"..." could fix some of this.  But it's been a long time since I last
played with invisible text.

Perhaps it would be worthwhile to experiment with putting the `display'
property over the hidden text (with "...") instead and see whether that
has fewer quirks.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-08-15 18:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 15:16 bug#21710: 25.0.50; self-insert-command before a folded outline inserts after the outline Oleh Krehel
2015-10-19 16:22 ` Eli Zaretskii
2015-10-21 13:05   ` Oleh Krehel
2015-10-21 17:02     ` Eli Zaretskii
2021-08-15 17:01 ` Lars Ingebrigtsen
2021-08-15 17:32   ` Eli Zaretskii
2021-08-15 18:12     ` Lars Ingebrigtsen [this message]
2021-08-15 18:30       ` Eli Zaretskii

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=87czqeinlx.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=21710@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=ohwoeowho@gmail.com \
    /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).