unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lektu@terra.es>
Cc: emacs-devel@gnu.org, F.J.Wright@qmul.ac.uk
Subject: Re: [F.J.Wright@qmul.ac.uk: rcs2log]
Date: Wed, 30 Oct 2002 08:43:06 +0100	[thread overview]
Message-ID: <20021030083724.5BCC.LEKTU@terra.es> (raw)
In-Reply-To: <7458-Tue29Oct2002223952+0200-eliz@is.elta.co.il>

On Tue, 29 Oct 2002 22:39:53 +0300, "Eli Zaretskii" <eliz@is.elta.co.il> wrote:

> Why is it fragile?

Because you are executing programs that you don't control (what if
trying a sort.exe causes a crash or any other kind of problem), and
because probably it'd fail if I happen to modify the PATH afterwards.
If I have to manually configure a variable and after a while I change
the path I'm more prone to remember it that if Emacs somehow configured
it behind my back.

> This would require users to customize the variable.  Without a proper
> customization, the relevant feature will be broken.

Sure. But we already have cases like these now, and they're resolved by
having -program variables. The first "find.exe" in my PATH is
C:\WINNT\system32\find.exe. Same for ftp and telnet. Ange-FTP didn't try
to find what was the "right" ftp, I manually configured
`ange-ftp-ftp-program'.

Having good defaults helps here.

                                                           /L/e/k/t/u

  reply	other threads:[~2002-10-30  7:43 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-26 20:16 [F.J.Wright@qmul.ac.uk: rcs2log] Richard Stallman
2002-10-28 16:57 ` Juanma Barranquero
2002-10-28 17:30 ` Juanma Barranquero
2002-10-29  6:03   ` Eli Zaretskii
2002-10-29  7:30     ` Juanma Barranquero
2002-10-29 10:21       ` Dr Francis J. Wright
2002-10-29 10:28         ` Juanma Barranquero
2002-10-29 14:47           ` Stefan Monnier
2002-10-29 15:07             ` Juanma Barranquero
2002-10-29 15:19               ` Stefan Monnier
2002-10-29 15:37                 ` Juanma Barranquero
2002-10-29 15:43                   ` Stefan Monnier
2002-10-29 17:06                     ` Dr Francis J. Wright
2002-10-29 19:22                       ` Stefan Monnier
2002-10-29 19:51                         ` Eli Zaretskii
2002-10-30 10:36                         ` Dr Francis J. Wright
2002-10-31 17:25                         ` Richard Stallman
2002-10-29 19:50                       ` Eli Zaretskii
2002-10-30 10:59                         ` Dr Francis J. Wright
     [not found]                           ` <200210301600.g9UG0VT22546@rum.cs.yale.edu>
2002-10-30 16:51                             ` rcs2log.bat Dr Francis J. Wright
2002-10-29 19:47                 ` [F.J.Wright@qmul.ac.uk: rcs2log] Eli Zaretskii
2002-10-30 10:29                   ` Dr Francis J. Wright
2002-10-29 16:36             ` Dr Francis J. Wright
2002-10-29 16:40               ` Stefan Monnier
2002-10-29 17:10                 ` Dr Francis J. Wright
2002-10-29 19:39       ` Eli Zaretskii
2002-10-30  7:43         ` Juanma Barranquero [this message]
2002-10-30 14:10           ` Eli Zaretskii
2002-10-30 14:41             ` Juanma Barranquero
2002-11-02 12:01               ` Francesco Potorti`
2002-10-31 17:26             ` Richard Stallman
2002-10-30 17:16       ` Richard Stallman

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=20021030083724.5BCC.LEKTU@terra.es \
    --to=lektu@terra.es \
    --cc=F.J.Wright@qmul.ac.uk \
    --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).