From: Bastien <bzg@altern.org>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode@gnu.org, reiner.steib@gmx.de
Subject: Re: Bug: Toggle descriptive and literal links [7.4]
Date: Tue, 23 Aug 2011 16:57:37 +0200 [thread overview]
Message-ID: <87hb58yun8.fsf@altern.org> (raw)
In-Reply-To: <m1zkj146sd.fsf@tsdye.com> (Thomas S. Dye's message of "Mon, 22 Aug 2011 08:53:22 -1000")
Hi Thomas,
tsd@tsdye.com (Thomas S. Dye) writes:
> Thanks for adding this. I work with literal links and this potentially
> saves time and effort.
>
> I wonder if I'm using it correctly? In .emacs I set
> org-link-display-descriptive nil and have:
>
> --------
> org-link-display-descriptive is a variable defined in `org.el'.
> Its value is nil
>
> Documentation:
> Non-nil means Org will display descriptive links.
> E.g. [[http://orgmode.org][Org website]] will be displayed as
> "Org Website", hiding the link itself and just displaying its
> description. When set to `nil', Org will display the full links
> literally.
>
> You can interactively set the value of this variable using the
> `org-toggle-link-display'.
> --------
>
> But when I open an Org-mode buffer I find the links displayed
> descriptively.
The initialization of the link display relied on
`org-descriptive-links' and I discover this variable (doh!)
So I've now remove `org-link-display-descriptive' and use
`org-descriptive-links' instead for backward compatibility.
Please use this variable too and let me know if things are
all right now.
Best,
--
Bastien
next prev parent reply other threads:[~2011-08-23 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 11:19 Bug: Toggle descriptive and literal links [7.4] Reiner Steib
2011-08-17 13:03 ` Bastien
2011-08-22 18:53 ` Thomas S. Dye
2011-08-23 14:57 ` Bastien [this message]
2011-08-23 17:12 ` Thomas S. Dye
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=87hb58yun8.fsf@altern.org \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=reiner.steib@gmx.de \
--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).