From: Damien Elmes <emacs-devel@repose.cx>
Subject: Re: last character on line different when behind invis text?
Date: Fri, 30 Aug 2002 01:28:19 +1000 [thread overview]
Message-ID: <86r8gh7kh8.fsf@mobile.repose.cx> (raw)
In-Reply-To: 86k7meb2jq.fsf@mobile.repose.cx
Damien Elmes <emacs-devel@repose.cx> writes:
> Sacha Chua <sacha@free.net.ph> writes:
>
>> (insert-string
>> (concat
>> "Line 1 with " (propertize "invisible text." 'invisible \t 'intangible t)
>> "\nLine 2 with " (propertize "invisible text." 'invisible t 'intangible t)
>> "\nLine 3 with visible text.\n"))
>
> After that text is inserted into the buffer in CVS, you can also see that (c-x
> =) doesn't identify the last char on a line as a C-j as in previous emacsen.
Okay, I've dug through intervals.c in an effort to find out what's going on.
The change appears to be related to adjust_for_invis_intang() which Miles B
added on 14/3.
I've found that I can return to the old behavior of previous emacsen (ie, c-k
on the first line will only kill to the end of the line), by turning off
rear-sticky, as adjust_for_invis_intang checks to see if the text properties
of the invis+intang text are sticky or not. So a line like so works:
"Line 1 with " (propertize "invisible text." 'invisible t 'intangible t
rear-nonsticky t)
It looks like the code I inherited was using some magic which has broken with
the new way invis+intangible text is handled. I'll look into that and see if I
can figure out what's going on before bothering you guys again.
Regards,
--
Damien Elmes
next prev parent reply other threads:[~2002-08-29 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-24 13:59 last character on line different when behind invis text? Damien Elmes
2002-08-26 0:36 ` Richard Stallman
2002-08-26 5:12 ` Sacha Chua
2002-08-26 5:40 ` Damien Elmes
2002-08-29 15:28 ` Damien Elmes [this message]
2002-08-31 16:58 ` Richard Stallman
2002-09-06 15:41 ` Damien Elmes
2002-09-07 10:29 ` Richard Stallman
2002-09-10 15:25 ` Damien Elmes
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=86r8gh7kh8.fsf@mobile.repose.cx \
--to=emacs-devel@repose.cx \
/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).