From: "T.V Raman" <raman@google.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: org-mode 9.6 and Emacs Built from Git HEAD
Date: Fri, 02 Dec 2022 07:09:51 -0800 [thread overview]
Message-ID: <p91a645alkw.fsf@google.com> (raw)
In-Reply-To: <87zgc6jfr1.fsf@localhost> (Ihor Radchenko's message of "Fri, 02 Dec 2022 09:50:58 +0000")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1069 bytes --]
I think I made some progress chasing this down:
1. Problem: With Emacspeak as implemented, org-fold-core-style set to
text-properties results in hidden links being spoken.
2. The underlying cause appears to be how copying such text into
another buffer works.
3. Emacspeak implements its core speech logic by copying over what is to
be spoken (text) to a scratch buffer, pre-processing it, and then
doing its work.
4. The "invisibility" gets lost in the new org fold implementation.
See here for the relevant logic and code.
I verified that the copy/insert to be the problem by:
A. Open an org file with a link in it with org-fold-core-style set to
text-properties.
B. Set mark and do
M-: (setq text (buffer-substring (point) (mark)))
C. Switch to a new buffer "foo"
M-: (insert-for-yank text)D. Insert:
E. Move point to the portion of the link that should be hidden and do
M-: (invisible-p (point)) Returns nil.
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2022-12-02 15:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 3:46 org-mode 9.6 and Emacs Built from Git HEAD T.V Raman
2022-12-01 1:31 ` Ihor Radchenko
2022-12-01 15:01 ` T.V Raman
2022-12-01 16:15 ` T.V Raman
2022-12-01 11:48 ` Ihor Radchenko
2022-12-01 21:31 ` T.V Raman
2022-12-02 5:08 ` Ihor Radchenko
[not found] ` <25482.2636.186975.666369@retriever.mtv.corp.google.com>
[not found] ` <87zgc6jfr1.fsf@localhost>
2022-12-02 15:09 ` T.V Raman [this message]
2022-12-04 3:37 ` T.V Raman
2022-12-05 4:13 ` T.V Raman
2022-12-07 12:29 ` Ihor Radchenko
[not found] ` <25488.44727.272656.782779@retriever.mtv.corp.google.com>
[not found] ` <878rjintu4.fsf@localhost>
[not found] ` <25489.63879.848634.401102@retriever.mtv.corp.google.com>
[not found] ` <87mt7y6ief.fsf@localhost>
[not found] ` <25490.266.362467.616997@retriever.mtv.corp.google.com>
[not found] ` <87k0317w2e.fsf@localhost>
[not found] ` <25490.4343.137735.654592@retriever.mtv.corp.google.com>
[not found] ` <87h6y57t0y.fsf@localhost>
[not found] ` <25490.6757.786967.103592@retriever.mtv.corp.google.com>
[not found] ` <87edt97qtt.fsf@localhost>
2022-12-18 4:12 ` T.V Raman
2022-12-18 12:56 ` Ihor Radchenko
2022-12-19 3:25 ` T.V Raman
2022-12-19 3:24 ` T.V Raman
2022-12-07 12:28 ` Ihor Radchenko
2022-12-01 7: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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p91a645alkw.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=yantar92@posteo.net \
/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.