unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: marmote-te <marmot-te@riseup.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43909@debbugs.gnu.org
Subject: bug#43909: 26.1; read syntax breaks prettify-symbols
Date: Mon, 20 Sep 2021 01:38:01 +0200	[thread overview]
Message-ID: <871r5kgmfs.fsf@riseup.net> (raw)
In-Reply-To: <87mtoczifk.fsf@gnus.org>


Lars Ingebrigtsen <larsi@gnus.org> writes:

> Sake <marmot-te@riseup.net> writes:
>
>> ?\" ;; 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)
>
> Thanks for the recipe -- I can reproduce this in Emacs 28, too (but only
> in org-mode).  Perhaps somebody with more experience with Org can take a
> look at this?

Hi M.Ingebrigtsen,

Definitively this is an org-mode issue.
I have another pseudo recipe that may be related to that parsing issue.

To compile gcc I have an org file that tangle to a a script and
there ...

#+begin_src bash :noweb-ref none :results pp
__banner "Verify authenticity"
gpg --verify /gcc-.tar.xz.sig
#+end_src

#+RESULTS:
#+begin_example
gpg: les données signées sont supposées être dans « /mnt/_/tar_gcc-10.2.0/gcc-10.2.0.tar.xz »
gpg: Signature faite le jeu. 23 juil. 2020 08:57:41 CEST
gpg:                avec la clef RSA 7F74F97C103468EE5D750B583AB00996FC26A641
 » [inconnu]
 » [inconnu]
 » [inconnu]
 » [inconnu]
gpg: Attention : cette clef n'est pas certifiée avec une signature de confiance.
gpg:             Rien n'indique que la signature appartient à son propriétaire.
Empreinte de clef principale : 1397 5A70 E63C 361C 73AE  69EF 6EEB 81F8 981C 74C7
   Empreinte de la sous-clef : 7F74 F97C 1034 68EE 5D75  0B58 3AB0 0996 FC26 A641
#+end_example

This is not the result expected ! Whole parts are disappearing !

I think that is reproducible anyway if you have a file to verify from an
org block, and show that double quote are somewhere breaking org mode
blocks. Or maybe that is another issue but always about double quotes
and org-mode ;)

Thanks you for your interest.
--





      reply	other threads:[~2021-09-19 23:38 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
2021-09-16 14:47         ` Lars Ingebrigtsen
2021-09-19 23:38           ` marmote-te [this message]

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=871r5kgmfs.fsf@riseup.net \
    --to=marmot-te@riseup.net \
    --cc=43909@debbugs.gnu.org \
    --cc=larsi@gnus.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 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).