all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <rms@gnu.org>
Cc: juri@jurta.org, eliz@gnu.org, emacs-devel@gnu.org
Subject: RE: bug#10385: e binding in info-mode
Date: Sat, 7 Jan 2012 23:02:54 -0800	[thread overview]
Message-ID: <BF95E20448704CD4AAE62716C93FA192@us.oracle.com> (raw)
In-Reply-To: <E1RjlSP-0005ZA-Qg@fencepost.gnu.org>

>     Why?  What if someone wants to create a small Info file 
>     and doesn't want to bother with texinfo or doesn't have the
>     conversion/make tools handy?
> 
> It is really preferable to write in Texinfo.

I wouldn't argue with that.  I'm sure you are right.

> I don't see a reason why we should want to encourage people
> to write Info files directly.

Mere existence of the command `Info-edit' is hardly encouragement.  Have you
noticed a problem with users being too encouraged to write Info files by hand
over the last 30 years?

And during that time they have even had a simple, advertised key binding for
`Info-edit', which binding is being removed now anyway.

> Have you encountered anyone who really wanted to do so?

Nope.  But if I had to edit an Info node (which has not been the case so far)
and I did not have texinfo, makeinfo, etc. on my laptop (which is the case), I
wouldn't hesitate to do it.

And note that the Info manual has a section, `Expert Info' (with 5 subsections),
that describes "how to write an Info file by hand" and how to "install it
manually".  That suggests at least as much encouragement to write Info files by
hand as does the mere existence of command `Info-edit'.

The manual does not at all say or suggest that writing Info files by hand is
useless.  What it says, in fact, is "_in most cases_, writing a Texinfo file is
better, since you can use it to make a printed manual or produce other formats,
such as HTML and DocBook, as well as for generating Info files".

"In most cases" is a far cry from always.  And surely if it were truly useless
to write Info files by hand we would not devote 6 nodes of the Info manual to
explaining in detail how to do it (?).

Granted, `Info-edit' is not the same as all that is discussed in the manual
under the topic of writing an Info file by hand.  But your question was about
writing an Info file by hand, and here is a far greater encouragement than
`Info-edit'.

AFAICT, we seem to be saying in the Info manual that there is a use case for
hand editing, even if we say that in most cases Texinfo is more useful.  Both
the Info manual and the lack of installed `makeinfo' for at least some users on
some systems (non-development laptops? phones? tablets?) argue that hand editing
is not useless.




  reply	other threads:[~2012-01-08  7:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-27 22:37 bug#10385: e binding in info-mode Karl Berry
2012-01-06  8:11 ` Glenn Morris
2012-01-06 15:54   ` Drew Adams
2012-01-06 16:07     ` Eli Zaretskii
2012-01-07  0:12       ` Richard Stallman
2012-01-07 20:27         ` Juri Linkov
2012-01-07 21:26           ` Drew Adams
2012-01-07 21:46             ` Juri Linkov
2012-01-07 22:15               ` Drew Adams
2012-01-07 23:10                 ` Juri Linkov
2012-01-07 23:27                   ` Drew Adams
2012-01-07 23:47                     ` Juri Linkov
2012-01-08  1:08                       ` Drew Adams
2012-01-08  5:38                         ` Richard Stallman
2012-01-08  7:03                           ` Drew Adams
2012-01-08  8:21                             ` Eli Zaretskii
2012-01-08 22:34                             ` Richard Stallman
2012-01-08 23:00                               ` Drew Adams
2012-01-09 15:55                                 ` Richard Stallman
2012-01-08  5:38             ` Richard Stallman
2012-01-08  7:02               ` Drew Adams [this message]
2012-01-08  5:37           ` Richard Stallman
2012-01-08 14:13           ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BF95E20448704CD4AAE62716C93FA192@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=rms@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.