From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Michael Brand <michael.ch.brand@gmail.com>,
Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Links in node-property
Date: Sat, 01 Mar 2014 23:05:01 +0100 [thread overview]
Message-ID: <87zjl9o9rm.fsf@gmail.com> (raw)
In-Reply-To: <87bnxp8vzf.fsf@bzg.ath.cx> (Bastien's message of "Sat, 01 Mar 2014 22:11:48 +0100")
Bastien <bzg@gnu.org> writes:
> Believe me, there *are* links in comments, I can see them :)
>
> Right now, hitting C-c C-o on this link
>
> # http://orgmode.org
>
> in an org-mode buffer produces the attached backtrace, which is
> a problem /per se/ (easily fixable, I guess.)
My bad. This should now be fixed.
> Anyway, not supporting links in comments does not feel right, as
> links in comments are both frequent and useful.
Comments, by definition, are dead data. It just doesn't make sense to
expect to have an active link, or timestamp, or whatever inside. If you
put an active timestamp in a comment, you don't expect it to show in the
agenda, right?
If you need live non-exportable data, you can stuff it in a regular
drawer.
> I'm sorry for the frustration it will inevitably create, but at this
> stage I suggest to simply revert the commits related to the rewriting
> of `org-open-at-point'. To my knowledge, there is no bug that this
> rewrite fixes, there is no gain in speed, and only a regression (not
> opening the next link) and a bug (see `org-agenda-open-link'.)
>
> What do you think?
I think that if we reverted each buggy commit, we wouldn't be far from
the very first commit in Org.
Anyway, I suggest to either explain to me why opening the next link is
needed, so we can discuss on how to do it best, or implement the feature
yourself, as you intended to do a few minutes ago.
In any case, I don't see the need to trash the few hours of work
I invested already in this (well, almost) working function.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2014-03-01 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 20:16 Links in node-property Michael Brand
2014-03-01 20:22 ` Nicolas Goaziou
2014-03-01 21:11 ` Bastien
2014-03-01 22:05 ` Nicolas Goaziou [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=87zjl9o9rm.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=michael.ch.brand@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).