From: Florian Beck <abstraktion@t-online.de>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Bastien <bzg@altern.org>,
emacs-orgmode@gnu.org, Florian Beck <abstraktion@t-online.de>
Subject: Re: Using org-mode for Research and Notetaking
Date: Tue, 19 Jul 2011 03:34:52 +0200 [thread overview]
Message-ID: <87hb6j2gub.fsf@sophokles.streitblatt.de> (raw)
In-Reply-To: <m1aacbjg3d.fsf@tsdye.com> (Thomas S. Dye's message of "Mon, 18 Jul 2011 13:59:02 -1000")
tsd@tsdye.com (Thomas S. Dye) writes:
> Bastien <bzg@altern.org> writes:
>
>> Hi Florian,
>>
>> Florian Beck <abstraktion@t-online.de> writes:
>>
>>> Actually, I meant »tags« in the HTML sense. For <boxed>example</boxed>
>>> would call a function during export, which returns, say, its LaTeX
>>> interpretation, another function would be called by font lock (or
>>> whatever you use) to determine its on screen display.
>>
>> Well, I'm not in favor of introducing <tag> -- they can be convenient,
>> but they degrade readability IMO.
>
> Aloha all,
>
> Perhaps they are [[tag:boxed][already]] here with org-add-link-type? It
> seems to me that all that's missing is a way to specify a function to
> determine on screen display.
Exactly. I don't care about the specific implementation (and org makes a
lot of my previous uses superflous). TAGs in the above sense – however
implemented – would allow for fine grain control of the output. For
example different classes of footnotes with latex/bogfoot or specific
handling of citations.
Readability is not the issue, imo, because currently my workaround would
be to put the whole paragraph in a latex source block – which certainly
doesn't improve readability. Tagged text, on the other hand, should and
could definity allow for its own on screen display.
What is an issue is that (apart from property/source blocks and
emphasis) org text is pretty much plain. TAGs could impair that.
Currently migrating from muse to org I can certainly attest that any
»special handling« certainly impairs portability.
--
Florian Beck
next prev parent reply other threads:[~2011-07-19 1:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 11:09 RFC: Revisit org-export-content-div (in the context of org-s5) Jambunathan K
2011-07-10 11:28 ` Jambunathan K
2011-07-11 11:44 ` Bastien
2011-07-11 19:55 ` Using org-mode for Research and Notetaking Florian Beck
2011-07-12 14:23 ` John Hendy
2011-07-14 18:09 ` Florian Beck
2011-07-12 14:28 ` Giovanni Ridolfi
2011-07-13 8:55 ` Bastien
2011-07-13 9:59 ` Sebastien Vauban
2011-07-13 11:20 ` Bastien
2011-07-13 12:20 ` Sebastien Vauban
2011-07-13 13:43 ` Nicolas Goaziou
2011-07-16 11:40 ` Bastien
2011-07-18 12:42 ` Matt Lundin
2011-07-18 13:21 ` Sebastien Vauban
2011-07-18 14:53 ` Matt Lundin
2011-07-18 14:03 ` Sebastien Vauban
2011-07-18 14:58 ` Bastien
2011-07-14 18:40 ` Florian Beck
2011-07-14 18:59 ` Thomas S. Dye
2011-07-18 22:54 ` Bastien
2011-07-18 23:59 ` Thomas S. Dye
2011-07-19 1:34 ` Florian Beck [this message]
2011-07-26 11:27 ` Bastien
2011-07-26 14:17 ` Florian Beck
2011-07-26 15:15 ` Thomas S. Dye
2011-07-26 17:41 ` Christian Moe
2011-07-11 11:44 ` RFC: Revisit org-export-content-div (in the context of org-s5) 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:
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=87hb6j2gub.fsf@sophokles.streitblatt.de \
--to=abstraktion@t-online.de \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).