From: John Kitchin <jkitchin@andrew.cmu.edu>
To: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: loss of text properties in org-export--generate-copy-script
Date: Tue, 27 Nov 2018 18:14:25 -0500 [thread overview]
Message-ID: <CAJ51ETpMnfROsJEjxj=cRjoL6XwMdfw+23UQq-YHuOUHyR=F1w@mail.gmail.com> (raw)
In-Reply-To: <87wooyrv9j.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
ok. I thought there might be a reason. I guess something like a read-only
property could be a problem if anything tries to change those. Are there
other properties you know of that could be problematic? maybe before/after
change properties? I think there are inhibit-* variables to avoid issues
with those if they become a problem.
I am still baffled on why the unusual workaround with message-box makes it
work though.
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Tue, Nov 27, 2018 at 5:49 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> > In the function org-export--generate-copy-script, the buffer contents are
> > copied over with buffer-substring-no-properties, so it appears that all
> > text properties are lost in the temporary copy.
> >
> > I wondered why that is done?
>
> I feel more comfortable when I can assume no text property will get in
> the way.
>
> I turned `buffer-substring-no-properties' into `buffer-string' in
> "master".
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 1973 bytes --]
prev parent reply other threads:[~2018-11-27 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 18:21 loss of text properties in org-export--generate-copy-script John Kitchin
2018-11-27 22:49 ` Nicolas Goaziou
2018-11-27 23:14 ` John Kitchin [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ51ETpMnfROsJEjxj=cRjoL6XwMdfw+23UQq-YHuOUHyR=F1w@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).