From mboxrd@z Thu Jan  1 00:00:00 1970
From: Florian Beck <abstraktion@t-online.de>
Subject: Re: Using org-mode for Research and Notetaking
Date: Tue, 19 Jul 2011 03:34:52 +0200
Message-ID: <87hb6j2gub.fsf@sophokles.streitblatt.de>
References: <81d3hi75oj.fsf@gmail.com> <818vs674t7.fsf@gmail.com>
	<87liw582jg.fsf@gnu.org> <87zkkktwwk.fsf_-_@sophokles.streitblatt.de>
	<87bowy4l0j.fsf@gnu.org> <87hb6oso2y.fsf@sophokles.streitblatt.de>
	<87pql7w679.fsf@gnu.org> <m1aacbjg3d.fsf@tsdye.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:52860)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <abstraktion@t-online.de>) id 1QizDS-0007fB-2j
	for emacs-orgmode@gnu.org; Mon, 18 Jul 2011 21:35:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <abstraktion@t-online.de>) id 1QizDM-0007yQ-EG
	for emacs-orgmode@gnu.org; Mon, 18 Jul 2011 21:35:17 -0400
Received: from mo-p05-ob.rzone.de ([81.169.146.181]:47439)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <abstraktion@t-online.de>) id 1QizDM-0007xt-2o
	for emacs-orgmode@gnu.org; Mon, 18 Jul 2011 21:35:12 -0400
In-Reply-To: <m1aacbjg3d.fsf@tsdye.com> (Thomas S. Dye's message of "Mon, 18
	Jul 2011 13:59:02 -1000")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: </archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Bastien <bzg@altern.org>, emacs-orgmode@gnu.org, Florian Beck <abstraktion@t-online.de>

tsd@tsdye.com (Thomas S. Dye) writes:

> Bastien <bzg@altern.org> writes:
>
>> Hi Florian,
>>
>> Florian Beck <abstraktion@t-online.de> writes:
>>
>>> Actually, I meant =C2=BBtags=C2=AB in the HTML sense. For <boxed>exampl=
e</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.=20
>>
>> 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.=20=20

Exactly. I don't care about the specific implementation (and org makes a
lot of my previous uses superflous). TAGs in the above sense =E2=80=93 howe=
ver
implemented =E2=80=93 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 =E2=80=93 which certa=
inly
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
=C2=BBspecial handling=C2=AB certainly impairs portability.

--=20
Florian Beck