From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ken Mankoff <mankoff@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: FR: Fontify links even when in comments
Date: Tue, 24 Feb 2015 09:13:08 +0100 [thread overview]
Message-ID: <87pp8z4tij.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2oaokqulw.fsf@gmail.com> (Ken Mankoff's message of "Mon, 23 Feb 2015 14:46:19 -0500")
Ken Mankoff <mankoff@gmail.com> writes:
> To me comments are mainly things that don't get exported.
Comments are much more than that. They also deactivate the syntax (which
is what I call "dead" syntax).
* Headline
# SCHEDULED: <2015-02-24 Tue>
(org-entry-get nil "SCHEDULED") => nil
> Their utility and data density is reduced if they can't contain links
> (or I can't see that the link is there, which is sort-of the same
> thing).
>
> When writing a document it is useful to leave informal notes to myself
> that say "see X" where X is an external file, or a section (or some
> code) elsewhere in this document, etc.
They cannot contain link, nor anything else. However, the feature you
describe above was deemed useful enough that `org-open-at-point'
sloppily opens anything looking like a link (or a timestamp) within
a comment.
However, there is, per syntax, no link there, and I don't think it
should be fontified.
Regards,
next prev parent reply other threads:[~2015-02-24 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 18:48 FR: Fontify links even when in comments Ken Mankoff
2015-02-23 19:32 ` Nicolas Goaziou
2015-02-23 19:46 ` Ken Mankoff
2015-02-24 8:13 ` Nicolas Goaziou [this message]
2015-02-24 12:53 ` Nicolas Richard
2015-02-24 14:10 ` Ken Mankoff
2015-02-24 14:37 ` Nicolas Goaziou
2015-02-24 15:05 ` Nicolas Richard
2015-02-24 19:57 ` Samuel Wales
2015-02-24 19:57 ` Samuel Wales
2015-02-24 20:02 ` Nicolas Goaziou
2015-02-24 20:26 ` Samuel Wales
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=87pp8z4tij.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@gmail.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/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).