From: Sake <marmot-te@riseup.net>
To: 43909@debbugs.gnu.org
Subject: bug#43909: 26.1; read syntax breaks prettify-symbols
Date: Tue, 13 Oct 2020 13:01:06 -0700 [thread overview]
Message-ID: <19346b08b5dd8b4cc05f42d6b9c29a61@riseup.net> (raw)
In-Reply-To: <87h7qzarfl.fsf@gnus.org>
Le 2020-10-13 00:41, Lars Ingebrigtsen a écrit :
> L : The destruction was that your " characters (0x22) are translated into “
> characters (0x201c) (and so on), so it's not valid Emacs Lisp any more.
> Please adjust the mail software you're using, because none of the code
> examples you're posting can be used by other people. (And re-send the
> example for bug reproduction.)
Sorry about that, if ever you want to know, it was a package which setup
org-mode in mu4e message which alter the quotation unless they are in a
source code block.
I think it will be ok now
> M : A recipe for emacs -Q and an explanation of what
> "interfere" exactly means would be nice
In the previous mail I forget the point : this bug appears in ~org-mode~
buffers.
Do I need to forward to another mailing list the issue ?
So in a scratch buffer, with emacs -Q, here the recipe :
(add-hook 'org-mode-hook 'prettify-symbols-mode)
?\" ;; after this point prettify does not behave correctly anymore
;; this will be a _lambda_ symbol when it should not
(setq-default prettify-symbols-alist '(("lambda" . 955)))
(org-mode)
(prettify-symbols-mode 0)
(prettify-symbols-mode 1)
;; this will not be a _lambda_ symbol when it should
lambda
?\" ;; after this point prettify behaves correctly again
;; this will be a _lambda_ symbol like it should
lambda
--
<:3nn~~
<:3nn~~
<:3nn~~
next prev parent reply other threads:[~2020-10-13 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 15:44 bug#43909: 26.1; read syntax breaks prettify-symbols marmot-te
2020-10-10 20:21 ` Lars Ingebrigtsen
2020-10-11 9:04 ` Michael Heerdegen
2020-10-12 17:24 ` marmot-te
2020-10-13 0:41 ` Lars Ingebrigtsen
2020-10-13 20:01 ` Sake [this message]
2021-09-16 14:47 ` Lars Ingebrigtsen
2021-09-19 23:38 ` marmote-te
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=19346b08b5dd8b4cc05f42d6b9c29a61@riseup.net \
--to=marmot-te@riseup.net \
--cc=43909@debbugs.gnu.org \
/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.