unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: "Lőrentey Károly" <Karoly.Lorentey@cern.ch>, emacs-devel@gnu.org
Subject: Re: Double slashes in config.h
Date: Sun, 20 Mar 2005 19:30:13 +0100	[thread overview]
Message-ID: <x5y8ci9nm2.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1DD4jx-0006ZL-NU@fencepost.gnu.org> (Richard Stallman's message of "Sun, 20 Mar 2005 13:01:29 -0500")

Richard Stallman <rms@gnu.org> writes:

> --ansi may have other consequences, and I don't trust it.
> Can we avoid generating these double-slashes?

I have had a bit of experience with this stuff in the installation
procedure of preview-latex and AUCTeX where several generated
directory names were passed through or into Lisp and caused trouble.

File name completion of directories in shells like bash adds the slash
automatically, so it is far too optimistic to assume that users won't
enter spurious slashes when specifying directory options.

One can clean up those names manually.  This is not necessarily
trivial, given that one would also want to remove trailing backslashes
on Windows.  And the experience was that there were almost always
oversights in that area whenever stuff got updated or rearranged.

And those are more or less minor packages and Makefiles.

So I'd say that it would be far too optimistic for a large project
like Emacs to rely on no double-slashes creeping up anywhere.

Yes, it can be done, but it is not something that works easily and can
be resolved without recurring time and again by accident.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-03-20 18:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20  5:43 Double slashes in config.h Lőrentey Károly
2005-03-20 18:01 ` Richard Stallman
2005-03-20 18:30   ` David Kastrup [this message]
2005-03-21 17:08     ` Lőrentey Károly
2005-03-21 17:30     ` Richard Stallman
2005-03-21 17:12   ` Lőrentey Károly
2005-03-22  3:34     ` 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=x5y8ci9nm2.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=Karoly.Lorentey@cern.ch \
    --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).