unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: xah lee <xahlee@gmail.com>
To: Mike Mattie <codermattie@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: paths are sensative to double separators
Date: Wed, 18 Mar 2009 19:50:37 -0700	[thread overview]
Message-ID: <aa6b5cbe0903181950q2999f1cele9747c6e89142583@mail.gmail.com> (raw)
In-Reply-To: <20090319015037.GC6695@reforged>

[-- Attachment #1: Type: text/plain, Size: 793 bytes --]

in unix-like OSes, double slash is effectively taken to mean root.
e.g. /foo/bar//baz.el would mean /baz.el
This convention is somewhat rooted in unixes.

 Xah

On Wed, Mar 18, 2009 at 6:50 PM, Mike Mattie <codermattie@gmail.com> wrote:

> Hi,
>
> I have noticed that paths in Emacs are sensitive to double separators e.g:
>
> (load /foo/bar/baz.el)  ;; works
> (load /foo/bar//baz.el) ;; broken
>
> The same behavior occurs with (find-file).
>
> This doesn't seem like a good thing. Is there a good reason for
> it that I am not aware of ?
>
> GNU Emacs 23.0.91.1 (i686-pc-linux-gnu, X toolkit) of 2009-03-07 on
> localhost
>
> Cheers,
> Mike Mattie
>
> --
> GnuPG Key: B9012279 is available from HKP server pgp.mit.edu
>



-- 
 Xah
∑ http://xahlee.org/

[-- Attachment #2: Type: text/html, Size: 1265 bytes --]

  reply	other threads:[~2009-03-19  2:50 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19  1:50 paths are sensative to double separators Mike Mattie
2009-03-19  2:50 ` xah lee [this message]
2009-03-19  5:42   ` Harald Hanche-Olsen
2009-03-19  6:54     ` Miles Bader
2009-03-19 16:33     ` David De La Harpe Golden
2009-03-19 19:37     ` Richard M Stallman
2009-03-20  0:38     ` xah lee
2009-03-19  9:48   ` Sebastian Rose
2009-03-19 11:16   ` Giorgos Keramidas
2009-03-19 14:20     ` Stephen J. Turnbull
2009-03-19 15:33       ` Giorgos Keramidas
2009-03-20  5:48         ` Stephen J. Turnbull
2009-03-20 12:57           ` Stefan Monnier
2009-03-20 14:55             ` Stephen J. Turnbull
2009-03-20 20:19               ` Stefan Monnier
2009-03-20 21:24                 ` Giorgos Keramidas
2009-03-20 22:56                   ` Sebastian Rose
2009-03-21  0:12                     ` Miles Bader
2009-03-21  4:43                   ` Stephen J. Turnbull
2009-03-21 16:04                     ` Giorgos Keramidas
2009-03-20 15:01             ` Eli Zaretskii
2009-03-20 20:14               ` Stefan Monnier
2009-03-19 15:47     ` Stefan Monnier
2009-03-19 19:08       ` Giorgos Keramidas
2009-03-19 23:59     ` Byung-Hee HWANG
2009-03-19  3:09 ` Miles Bader
2009-03-19 10:26   ` Sebastian Rose
2009-03-19 15:46     ` Miles Bader
2009-03-19 20:32     ` Stefan Monnier
2009-03-19 21:18       ` Sebastian Rose
2009-03-19 13:33   ` Stefan Monnier
2009-03-19 17:50     ` Mike Mattie
2009-03-19 20:34       ` Stefan Monnier
2009-03-19 21:32         ` Mike Mattie
  -- strict thread matches above, loose matches on Subject: below --
2009-03-19 21:25 Xavier Maillard

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=aa6b5cbe0903181950q2999f1cele9747c6e89142583@mail.gmail.com \
    --to=xahlee@gmail.com \
    --cc=codermattie@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=xah@xahlee.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).