From: Hrvoje Niksic <hniksic@xemacs.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: A way to export agenda with links into org-files to html ?
Date: Wed, 02 Mar 2011 09:48:24 +0100 [thread overview]
Message-ID: <8739n56h7r.fsf@xemacs.org> (raw)
In-Reply-To: <8762s2n2pw.fsf@gnu.org> (Bastien's message of "Tue, 01 Mar 2011 18:57:15 +0100")
Bastien <bzg@altern.org> writes:
> I see. So (thing-at-point 'url) would return the url/uri depending on
> that 'uri-ref property. But as far as I've understood, thing-at-point
> does not rely on properties -- am I wrong?
I am proposing a new property which currently available software of
course does not support. If we promote it, maybe programmers of these
other modes will like it enough to support it.
> Unless such a property can be used with thing-at-point (for
> `browse-url' and other commands), I'd rather put the burden of finding
> the proper ref to htmlize, based on the help-echo area...
>
> What do you think?
I think that the help-echo text is not a robust way to detect URLs. For
example, org-mode's help-echo text is "LINK: url", someone else will use
just the URL, others will translate "link", and yet others will not use
help-echo at all.
Modes need a reliable way to tell htmlize (and other interesting
parties) about URI references in the buffer. A property seems like an
obvious way to do so, and I'd prefer the property not to be specific to
htmlize.
next prev parent reply other threads:[~2011-03-02 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 21:46 A way to export agenda with links into org-files to html ? Marc-Oliver Ihm
2011-02-11 16:34 ` Bastien
2011-02-16 20:06 ` Hrvoje Niksic
2011-02-18 9:30 ` Bastien
2011-02-18 9:42 ` Hrvoje Niksic
2011-02-26 9:45 ` Bastien
2011-02-28 23:00 ` Hrvoje Niksic
2011-03-01 17:57 ` Bastien
2011-03-02 8:48 ` Hrvoje Niksic [this message]
2011-02-21 21:40 ` Marc-Oliver Ihm
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=8739n56h7r.fsf@xemacs.org \
--to=hniksic@xemacs.org \
--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).