emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: emacs-orgmode@gnu.org
Subject: Re: Feature request: Select links by description [7.4]
Date: Thu, 15 Sep 2011 16:39:19 -0400	[thread overview]
Message-ID: <m24o0dsfpk.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: AANLkTi=EoLd4ZtH5=k3sXYGf3YezMF3nwVBU8_p8TgmU@mail.gmail.com


on Tue Feb 15 2011, Dave Abrahams <dave-AT-boostpro.com> wrote:

> On Mon, Feb 14, 2011 at 11:14 PM, Bastien <bastien.guerry@wikimedia.fr> wrote:
>> Dave Abrahams <dave@boostpro.com> writes:
>
>>
>>> How about just always showing the link as it will be presented to the
>>> user first, followed by the raw link?  Then everything will be
>>> consistent.
>>
>> I don't see how it would prevent the problem I've been mentionning: we
>> will still have a mix of descriptions and raw links... or maybe I miss
>> something?
>
> If it's really paramount to avoid a mixture, you must hide all
> descriptions, which would be a step in the wrong direction for me.
>
>> I'm willing to improve the display of links, keep brainstorming!
>
> I'm out of ideas.  Leading off with the displayed form of the link is
> the best I can do.

<bump>

The best is the enemy of the good and all that... is there any reason
this can't be made to work?

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com

  reply	other threads:[~2011-09-15 20:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 14:27 Feature request: Select links by description [7.4] Dave Abrahams
2011-02-11 12:05 ` Bastien
2011-02-13 21:19   ` Dave Abrahams
2011-02-14 10:17     ` Bastien
2011-02-14 11:55       ` Dave Abrahams
2011-02-15  4:14         ` Bastien
2011-02-15  6:56           ` Dave Abrahams
2011-09-15 20:39             ` Dave Abrahams [this message]
2011-09-16  1:35               ` Dave Abrahams

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=m24o0dsfpk.fsf@pluto.luannocracy.com \
    --to=dave@boostpro.com \
    --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).