From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Moe Subject: Re: text color + highlight Date: Wed, 11 Aug 2010 01:02:09 +0200 Message-ID: <4C61DA71.5020402@christianmoe.com> References: <87pqxw5cb1.fsf@gnu.org> <87mxszcsuv.fsf@gmail.com> <87d3tvru38.fsf@gmail.com> <87iq3kkef1.fsf@gmail.com> <4C60EE48.6030106@christianmoe.com> <532CED92-88AD-46F6-BC67-9D0DEDAA6D71@gmail.com> <4C611C24.2030601@christianmoe.com> <87pqxq4icv.fsf@gmail.com> <4C619CB5.70409@christianmoe.com> <877hjyw3js.wl%dmaus@ictsoc.de> Reply-To: mail@christianmoe.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=39264 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oixsy-0004ar-PK for emacs-orgmode@gnu.org; Tue, 10 Aug 2010 19:05:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Oixom-00067v-CT for emacs-orgmode@gnu.org; Tue, 10 Aug 2010 19:01:13 -0400 Received: from mail-forward1.uio.no ([129.240.10.70]:34767) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Oixol-00067m-UM for emacs-orgmode@gnu.org; Tue, 10 Aug 2010 19:01:12 -0400 Received: from exim by mail-out1.uio.no with local-bsmtp (Exim 4.69) (envelope-from ) id 1Oixok-0003t4-5E for emacs-orgmode@gnu.org; Wed, 11 Aug 2010 01:01:10 +0200 In-Reply-To: <877hjyw3js.wl%dmaus@ictsoc.de> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: David Maus Cc: emacs-orgmode@gnu.org I wrote (against my own suggestion): >> A drawback with using links for markup is that the user sees things that >> look like links, but do nothing when clicked, except give error messages. David Maus wrote: > It's not just a drawback but a more fundamental problem: This solution > abolishes the semantics of a fundamental entity, the link. color:red > /means/ something completely different than info:elisp. I certainly see that objection. I don't have a strong opinion, I just hit on the idea of using custom links as a quick hack to do some inline semantic tagging I wanted, then thought it might be worth considering in the present discussion, as an alternative to complex new syntaxes. Quibble: Note that =info:elisp= also means something rather different from =shell: ls *org=, =elisp: org-agenda=, or =elisp:(find-file-other-frame "Elisp.org")=. Okay, so Org-babel might put these link types out of business (and anyway they unfailingly crash my Emacs 23 for the Mac). But currently they /are/ defined as Org links, even though "execute this code" does not mean "follow this link". So the double-bracket syntax seems to have a broader meaning. Admittedly, though, all the currently defined link types mean "do something when clicked", which a =color:red= link does not. Christian