From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
acm@muc.de, gregory@heytings.org, mattiase@acm.org,
philipk@posteo.net, silent2600@gmail.com, emacs-devel@gnu.org
Subject: Re: emacs master + org Wrong type argument: number-or-marker-p
Date: Thu, 04 Aug 2022 14:19:20 +0800 [thread overview]
Message-ID: <87tu6sa5uf.fsf@yahoo.com> (raw)
In-Reply-To: <83o7x04kul.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 04 Aug 2022 08:51:46 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> What will we do with the "rare" exceptions, such as CC Mode, for
> example?
Fix them, individually?
> And what will we do with (I expect) the much larger group which
> becomes broken when font-lock stops widening, and their assumptions
> about being always able to access any buffer position become false?
We don't have make font lock avoid widening -- what I was proposing was
to ensure that font lock, CC Mode, and any other exceptions that might
come up only widen to the "locked" restriction, without changing the
behavior of narrow-to-region and friends.
The end result is the same as the current code, but the behavior of
narrow-to-region is not changed.
next prev parent reply other threads:[~2022-08-04 6:19 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 13:13 emacs master + org Wrong type argument: number-or-marker-p hx
2022-08-01 13:37 ` Eli Zaretskii
2022-08-01 15:11 ` Philip Kaludercic
2022-08-01 15:52 ` Eli Zaretskii
2022-08-01 16:07 ` Philip Kaludercic
2022-08-01 16:34 ` Visuwesh
2022-08-01 16:11 ` Gregory Heytings
2022-08-01 16:25 ` Eli Zaretskii
2022-08-01 16:34 ` Philip Kaludercic
2022-08-01 16:39 ` Eli Zaretskii
2022-08-01 17:15 ` Mattias Engdegård
2022-08-01 17:24 ` Eli Zaretskii
2022-08-01 17:36 ` Mattias Engdegård
2022-08-01 17:59 ` Eli Zaretskii
2022-08-01 18:06 ` Gregory Heytings
2022-08-01 18:25 ` Eli Zaretskii
2022-08-01 19:14 ` Gregory Heytings
2022-08-01 18:47 ` Mattias Engdegård
2022-08-01 19:16 ` Gregory Heytings
2022-08-01 20:05 ` Alan Mackenzie
2022-08-02 13:46 ` Eli Zaretskii
2022-08-02 18:59 ` Alan Mackenzie
2022-08-02 19:15 ` Eli Zaretskii
2022-08-02 20:28 ` Alan Mackenzie
2022-08-03 1:21 ` Po Lu
2022-08-03 2:38 ` Eli Zaretskii
2022-08-03 4:34 ` Po Lu
2022-08-03 12:02 ` Eli Zaretskii
2022-08-03 12:07 ` Po Lu
2022-08-03 12:34 ` Eli Zaretskii
2022-08-03 13:10 ` Po Lu
2022-08-03 13:36 ` Eli Zaretskii
2022-08-04 1:04 ` Po Lu
2022-08-04 1:09 ` Gregory Heytings
2022-08-04 1:27 ` Po Lu
2022-08-04 6:45 ` Eli Zaretskii
2022-08-03 20:47 ` Stefan Monnier
2022-08-04 5:51 ` Eli Zaretskii
2022-08-04 6:19 ` Po Lu [this message]
2022-08-04 7:10 ` Eli Zaretskii
2022-08-04 7:31 ` Po Lu
2022-08-04 7:58 ` Eli Zaretskii
2022-08-04 8:42 ` Po Lu
2022-08-04 9:06 ` Eli Zaretskii
2022-08-04 10:18 ` Alan Mackenzie
2022-08-04 13:18 ` Eli Zaretskii
2022-08-04 16:07 ` Alan Mackenzie
2022-08-04 16:37 ` Eli Zaretskii
2022-08-04 10:26 ` Po Lu
2022-08-04 11:33 ` Werner LEMBERG
2022-08-04 13:10 ` Eli Zaretskii
2022-08-04 21:56 ` Stefan Monnier
2022-08-03 7:21 ` Gregory Heytings
2022-08-03 11:07 ` Po Lu
2022-08-03 12:25 ` Eli Zaretskii
2022-08-03 15:25 ` Gregory Heytings
2022-08-04 1:02 ` Po Lu
2022-08-04 1:08 ` Gregory Heytings
2022-08-04 9:14 ` Stefan Monnier
2022-08-05 3:19 ` Richard Stallman
2022-08-03 8:57 ` Stefan Monnier
2022-08-03 11:05 ` Po Lu
2022-08-03 11:50 ` Eli Zaretskii
2022-08-02 8:25 ` Mattias Engdegård
2022-08-02 8:43 ` Gregory Heytings
2022-08-02 8:28 ` Stefan Monnier
2022-08-02 8:40 ` Mattias Engdegård
2022-08-01 16:36 ` Gregory Heytings
2022-08-01 16:49 ` Lars Ingebrigtsen
2022-08-01 17:23 ` Andreas Schwab
2022-08-07 15:22 ` Julien Cubizolles
2022-08-01 16:39 ` Andreas Schwab
2022-08-02 16:37 ` Opcode Versioning Was: " Sam Steingold
2022-08-02 22:10 ` Stefan Monnier
2022-08-04 14:59 ` Sam Steingold
2022-08-04 22:11 ` Stefan Monnier
2022-08-02 8:59 ` Po Lu
-- strict thread matches above, loose matches on Subject: below --
2022-08-01 13:45 Gerd Möllmann
2022-08-01 17:36 Gerd Möllmann
2022-08-01 17:58 ` Lars Ingebrigtsen
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=87tu6sa5uf.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=mattiase@acm.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--cc=silent2600@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.