From: Brady Trainor <algebrat@uw.edu>
To: emacs-orgmode@gnu.org
Subject: Re: hyperlink to customize
Date: Wed, 11 Dec 2013 05:57:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20131211T063614-897@post.gmane.org> (raw)
In-Reply-To: 87txegjqq2.fsf@alphaville.bos.redhat.com
Nick Dokos <ndokos <at> gmail.com> writes:
> Yes, you will be happiest when you are assimilated
:borg:
> > Would be nice to have org versions of all info files.
>
> [...] why do you
> want to have org versions of all info files? What would the benefits
> be?
>
> [...] But rewriting
> existing texinfo documentation in org just does not seem to
> provide many (or even any) benefits.
(disclaimer: my naïve impression)
- clarifications
- maybe not /all/ info files should be converted
- elisp and maybe the main Emacs manuals may be considered more pivotal
to all users and all modes
- maybe only a conversion to outline mode?
- I don't know if that has the potential for hyperlinks, but may supply
all the info functionality; is outline mode "lighter"?
- drawbacks
- slow (large elisp info file in org)
- hard to convert info to org?
- positives
- another way to look at the info (like a change of coordinates ;) )
- org's outline mode supplies one less step between browsing the
section titles and reading the content in unfolding, easier to navigate
especially, there is the effect that it may be hard to know where to look
for a possible elisp command, and so the more aids in browsing for that
command, the better.
prev parent reply other threads:[~2013-12-11 5:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 21:01 hyperlink to customize Brady Trainor
2013-12-09 21:14 ` Nick Dokos
2013-12-09 21:40 ` Brady Trainor
2013-12-09 22:06 ` Nick Dokos
2013-12-10 1:56 ` Brady Trainor
2013-12-10 15:41 ` Nick Dokos
2013-12-10 20:10 ` Brady Trainor
2013-12-10 21:23 ` Brady Trainor
2013-12-10 22:17 ` Nick Dokos
2013-12-11 5:57 ` Brady Trainor [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20131211T063614-897@post.gmane.org \
--to=algebrat@uw.edu \
--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).