unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "T.V Raman" <raman@google.com>
Cc: emacs-devel@gnu.org
Subject: Re: org-mode 9.6 and Emacs Built from Git HEAD
Date: Wed, 07 Dec 2022 12:28:40 +0000	[thread overview]
Message-ID: <87359rgzyf.fsf@localhost> (raw)
In-Reply-To: <p918rjnzvoh.fsf@google.com>

"T.V Raman" <raman@google.com> writes:

> While we wait for a clean way for a third-party app to handle this, can
> you tell me what I need to do on my end, e.g. perhaps inherit some magic
> property from the source buffer into the scratch buffer where I
> manipulate the text before speaking it perhaps?

Maybe just a simple `org-copy-visible'?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  parent reply	other threads:[~2022-12-07 12:28 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
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 [this message]
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

  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=87359rgzyf.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.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 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).