emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: returning propertized strings
Date: Sun, 21 May 2017 17:21:11 -0400	[thread overview]
Message-ID: <CAJ51ETrp4RCPnY_fLPqBJojOHo9-+rjyQQB+TPUu_g3f-nCZBA@mail.gmail.com> (raw)
In-Reply-To: <CAJ51ETqJO9ANwXu+L4aA=ahC5ptWZL16aWtmHyz7USw=2ZhTGw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1925 bytes --]

I figured out the properties are getting lost in org-babel-format-result,
in the beginning with (setq result (org-no-properties result)).

I can see a reason this is desirable is that the properties would not be
persistent on saving/closing. On the other hand, it could be really useful
in some scenarios where temporary properties would be useful.

Are there other reasons having properties on strings in the output are not
desirable?

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 Sun, May 21, 2017 at 9:04 AM, John Kitchin <jkitchin@andrew.cmu.edu>
wrote:

>
>
> On Sat, May 20, 2017 at 9:46 PM, Charles C. Berry <ccberry@ucsd.edu>
> wrote:
>
>> On Sat, 20 May 2017, John Kitchin wrote:
>>
>> If I run this block I get test as a result, but all its properties have
>>> been stripped.
>>>
>>> #+BEGIN_SRC emacs-lisp :results drawer
>>> (propertize "test" 'font-lock-face '(:foreground "red") 'help-echo
>>> "tooltip")
>>> #+END_SRC
>>>
>>> #+RESULTS:
>>> :RESULTS:
>>> test
>>> :END:
>>>
>>> Does anyone know where this happens and if it can be avoided?
>>>
>>
>> Where?
>>
>> Not sure, but late enough that `:results pp' will print them or `:post
>> ...' will receive them in `*this*'.
>>
>> #+BEGIN_SRC emacs-lisp :results drawer pp
>> (propertize "test" 'font-lock-face '(:foreground "red") 'help-echo
>> "tooltip")
>> #+END_SRC
>>
>> #+RESULTS:
>> : #("test" 0 4
>> :   (help-echo "tooltip" font-lock-face
>> :            (:foreground "red")))
>>
>
> I get this too, but  I really want test to actually be red, and have a
> tooltip in the results, and neither of these two methods seem to achieve
> that.
>
>
>>
>> also `*this*' will contain the propertized version if you use the :post
>> header arg.
>>
>> HTH,
>>
>> Chuck
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 3356 bytes --]

      reply	other threads:[~2017-05-21 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-20 22:59 returning propertized strings John Kitchin
2017-05-21  1:46 ` Charles C. Berry
2017-05-21 13:04   ` John Kitchin
2017-05-21 21:21     ` 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=CAJ51ETrp4RCPnY_fLPqBJojOHo9-+rjyQQB+TPUu_g3f-nCZBA@mail.gmail.com \
    --to=jkitchin@andrew.cmu.edu \
    --cc=ccberry@ucsd.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).