unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Problems with info (emacs version)
Date: Tue, 03 Jun 2003 00:06:44 -0400	[thread overview]
Message-ID: <E19N34O-0006SH-2L@fencepost.gnu.org> (raw)
In-Reply-To: <200306020333.h523XMC23468@eel.dms.auburn.edu> (message from Luc Teirlinck on Sun, 1 Jun 2003 22:33:22 -0500 (CDT))

    1.  Easiest one to fix:

	(info)Help-M

	which is used in the tutorial, *only* describes menus as they
	appear in the standalone info, not as they appear in the emacs
	version and the two are very different.

Would you please tell me the specific differences?  I scanned through
that none and did not notice anything incorrect.

    5.  Last and definitely worst.  The user copies part of the info
	buffer into an emacs mail buffer for somebody elses information.
	What the receiver receives is not what the sender believes he
	sent.  Granted, the hidden text does not exactly consist of
	obscenities or such (although I did not yet try to read these node
	names backward to get all the Satanic messages), but this is still
	really bad.

I am surprised you think this is such a serious issue.
Could you provide a test case where it causes a real problem?

  parent reply	other threads:[~2003-06-03  4:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02  3:33 Problems with info (emacs version) Luc Teirlinck
2003-06-02  4:29 ` Eli Zaretskii
2003-06-02  6:51   ` Kenichi Handa
2003-06-03  4:06   ` Richard Stallman
2003-06-03  4:18     ` Luc Teirlinck
2003-06-02 17:17 ` Stefan Monnier
2003-06-02 18:23   ` Luc Teirlinck
2003-06-03  4:06 ` Richard Stallman [this message]
2003-06-03  4:45   ` Luc Teirlinck
2003-06-03 18:03     ` Robert J. Chassell
2003-06-03 18:38       ` Luc Teirlinck
2003-06-03  5:22   ` Luc Teirlinck
2003-06-03  5:58     ` Simon Josefsson
2003-06-03  6:07       ` Miles Bader
2003-06-03  6:35         ` Simon Josefsson
2003-06-03  6:46           ` Miles Bader
2003-06-03 19:15             ` Simon Josefsson
2003-06-03 19:25               ` Miles Bader
2003-06-03 19:46                 ` Simon Josefsson
2003-06-03 19:58                   ` Luc Teirlinck
2003-06-03 20:05                     ` Simon Josefsson
2003-06-03 23:26                   ` Miles Bader
2003-06-03 13:49       ` Luc Teirlinck
2003-06-03 14:56         ` David Kastrup
2003-06-03 16:23           ` Stefan Monnier
2003-06-03 16:24           ` Luc Teirlinck
2003-06-05  0:08             ` Richard Stallman
2003-06-03 16:45           ` Luc Teirlinck
2003-06-03 19:23         ` Simon Josefsson
2003-06-03 19:40           ` Luc Teirlinck
2003-06-05  0:07         ` Richard Stallman
2003-06-03 14:07       ` Luc Teirlinck
2003-06-03 18:11     ` Robert J. Chassell
2003-06-04  8:53     ` Richard Stallman
2003-06-04 18:05       ` Luc Teirlinck

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=E19N34O-0006SH-2L@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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).