From: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Missing follow-links in descr-text
Date: Mon, 13 Feb 2006 20:49:23 +0100 [thread overview]
Message-ID: <43F0E2C3.60508@gmx.at> (raw)
In-Reply-To: <878xsf86x7.fsf@jurta.org>
> Instead of adding `follow-link t' to each and every place, what do you
> think about fixing this at the top level with the following patch?
>
> + (put 'default-button 'follow-link t)
That's what I had in my .emacs till today. It's an abuse of the button
idea, nevertheless. Although, the plethora of follow-links derived from
help-xref could serve as an excuse. With other words, practically each
and every use of default-button already has a follow-link property,
hence why not store it at "top level" in the first place.
prev parent reply other threads:[~2006-02-13 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 17:17 Missing follow-links in descr-text martin rudalics
2006-02-13 17:59 ` Juri Linkov
2006-02-13 19:49 ` martin rudalics [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43F0E2C3.60508@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@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.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).