From: Byung-Hee HWANG <bh@izb.knu.ac.kr>
To: Giorgos Keramidas <keramida@ceid.upatras.gr>
Cc: xah@xahlee.org, Mike Mattie <codermattie@gmail.com>, emacs-devel@gnu.org
Subject: Re: paths are sensative to double separators
Date: Fri, 20 Mar 2009 08:59:21 +0900 [thread overview]
Message-ID: <uab7hnjxi.fsf@izb.knu.ac.kr> (raw)
In-Reply-To: <87skl97og1.fsf@kobe.laptop> (Giorgos Keramidas's message of "Thu\, 19 Mar 2009 13\:16\:14 +0200")
Giorgos Keramidas <keramida@ceid.upatras.gr> writes:
> On Wed, 18 Mar 2009 19:50:37 -0700, xah lee <xahlee@gmail.com> wrote:
>> 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.
>
> Not really, no:
>
> keramida@kobe:/home/keramida$ cd /etc//security
> keramida@kobe:/etc/security$ pwd
> /etc/security
SunOS's screenshot:
$ uname -a
SunOS rose0 5.9 Generic_122300-13 sun4u sparc SUNW,Sun-Fire-880
$ pwd
/user2/hak/z9618029
$ cd /etc//security
$ pwd
/etc/security
$
> Having said that, I see that a double slash in find-file's prompt starts
> over from the filesystem root. That's slightly annoying when trying to
> open a filename with double slashes, but it's also helpful when one
> really *wants* to start over from the root of the filesystem :/
Sincerely,
--
Byung-Hee HWANG, KNU
∑ WWW: http://izb.knu.ac.kr/~bh/
next prev parent reply other threads:[~2009-03-19 23:59 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uab7hnjxi.fsf@izb.knu.ac.kr \
--to=bh@izb.knu.ac.kr \
--cc=codermattie@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=keramida@ceid.upatras.gr \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.