emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: syntax highlighting of elisp:blahblah and shell:blablah [8.2.6 (8.2.6-67-g9e09b2-elpa @ c:/Users/andrea/AppData/Roaming/.emacs.d/elpa/org-20140602/)]
Date: Sun, 20 Jul 2014 14:08:31 -0400	[thread overview]
Message-ID: <87mwc3c38g.fsf@gmail.com> (raw)
In-Reply-To: 84r41gji7h.fsf@gmail.com

Andrea Rossetti <andrea.rossetti@gmail.com> writes:

>   when I insert some text like "elisp:sometext" or "shell:sometext"
> in an Org buffer, it becomes highlighted and clickable. On click,
> a prompt asks for confirm to execute "sometext".
>   I get the same behaviour if I add tags to a headline, and one
> of the tags is "elisp" or "shell".
>   I expected this behaviour when I create links with double square
> brackets, but not in default text paragraphs, nor in the tags.
> May I please ask for some feedback:
> 1) did I miss something, and this was expected (at least for default
>    text paragraphs)?

I don't know whether it's expected (one of these years I really have
to sit down and learn the syntax).

> 2) is this reproducible for some of you as well?


>   I attach here a small test case:
> * my elisp tricks collection                            :elisp:andrea:tricks:
> I like to write elisp:it is useful.
> I seldow use shell:but it's useful as well


- in text, leave a space after the colon - that's standard practice

- in tags, put the `link' tag at the end:


The latter doesn't help if you have two `link'-type tags, but it should cover
the majority of problematic cases.


  reply	other threads:[~2014-07-20 18:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-20 13:03 Bug: syntax highlighting of elisp:blahblah and shell:blablah [8.2.6 (8.2.6-67-g9e09b2-elpa @ c:/Users/andrea/AppData/Roaming/.emacs.d/elpa/org-20140602/)] Andrea Rossetti
2014-07-20 18:08 ` Nick Dokos [this message]
2014-07-21 18:28   ` Andrea Rossetti
2014-07-27 13:58     ` Bastien

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:

  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=87mwc3c38g.fsf@gmail.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).