unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>, 1284@emacsbugs.donarmstrong.com
Cc: emacs-pretest-bug@gnu.org, bug-gnu-emacs@gnu.org
Subject: bug#1284: 23.0.60; ^M throughout Viper manual
Date: Fri, 31 Oct 2008 20:41:21 +0200	[thread overview]
Message-ID: <uej1wwqsu.fsf@gnu.org> (raw)
In-Reply-To: <002a01c93b75$5e26e6f0$0200a8c0@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Fri, 31 Oct 2008 09:26:02 -0700
> Cc: 
> 
> Also, the manual name should be listed in `dir' as `Viper', not `VIPER'.
> Throughout the Viper manual, Viper is referred to as `Viper', not `VIPER'.

We just honor the manual's request here, which specifies this DIR
entry in viper.texi:

    @direntry
    * VIPER: (viper).       The newest Emacs VI-emulation mode.
			      (also, A VI Plan for Emacs Rescue
			       or the VI PERil.)
    @end direntry

So it sounds like VIPER is actually an acronym, or at least it used to
be.






  reply	other threads:[~2008-10-31 18:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f7ccd24b0808060409x7317e093i6918324c0c057687@mail.gmail.com>
     [not found] ` <E1KQiBD-00055e-Ie@etlken.m17n.org>
     [not found]   ` <f7ccd24b0808060614h4917f240oc261b8fedff0e8d0@mail.gmail.com>
     [not found]     ` <E1KQtgD-0007i9-1n@etlken.m17n.org>
     [not found]       ` <jwvprokfvbs.fsf-monnier+emacs@gnu.org>
     [not found]         ` <00aa01c951a0$4535a2d0$0200a8c0@us.oracle.com>
     [not found]           ` <u1vwvh3vk.fsf@gnu.org>
2009-01-10 11:15             ` ^M in the info files Eli Zaretskii
2008-09-03 16:39               ` bug#876: ^M in some Windows info files because of null-byte detection Juanma Barranquero
2009-01-10 11:25                 ` bug#876: marked as done (^M in some Windows info files because of null-byte detection) Emacs bug Tracking System
2008-10-08  6:49               ` bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line Drew Adams
2008-10-08  8:02                 ` Juanma Barranquero
2008-10-08 10:01                   ` Eli Zaretskii
2008-10-08 16:52                     ` Juanma Barranquero
2008-10-08 14:10                   ` Drew Adams
2009-01-10 11:25                 ` bug#1117: marked as done (23.0.60; Index in Elisp manual has ^M at the end of each line) Emacs bug Tracking System
2008-10-31 15:56               ` bug#1284: 23.0.60; ^M throughout Viper manual Drew Adams
2008-10-31 16:26                 ` Drew Adams
2008-10-31 18:41                   ` Eli Zaretskii [this message]
2008-10-31 16:26                 ` Juanma Barranquero
2008-10-31 20:47                 ` Leo
2009-01-10 11:25                 ` bug#1284: marked as done (23.0.60; ^M throughout Viper manual) Emacs bug Tracking System
2009-01-07 11:55               ` bug#1816: 23.0.60; ^M in CC mode manual Matzi Kratzi
2009-01-07 14:05                 ` Jason Rumney
2009-01-07 14:15                   ` Processed: " Emacs bug Tracking System
2009-01-10 11:25                 ` bug#1816: marked as done (23.0.60; ^M in CC mode manual.) Emacs bug Tracking System
2009-01-10 16:21               ` ^M in the info files Drew Adams
     [not found]                 ` <handler.1845.B.12316045139313.ack@emacsbugs.donarmstrong.com>
2009-01-10 17:11                   ` bug#1845: Acknowledgement (^M in the info files) Drew Adams
2009-01-12 20:54               ` ^M in the info files Stefan Monnier
2009-01-12 22:13                 ` Eli Zaretskii
2009-01-12 22:27                   ` bug#876: " Glenn Morris
     [not found]                   ` <iyhc44cg94.fsf@fencepost.gnu.org>
2009-01-13  4:01                     ` Eli Zaretskii

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=uej1wwqsu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=1284@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-pretest-bug@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).