Date: Mon, 4 May 2009 20:41:20 +0200 From: Polytropon <freebsd@edvax.de> To: Ruben de Groot <mail25@bzerk.org> Cc: PJ <af.gourmet@videotron.ca>, freebsd-questions@freebsd.org Subject: Re: lost+found Message-ID: <20090504204120.31a34cc8.freebsd@edvax.de> In-Reply-To: <20090504090804.GA66641@ei.bzerk.org> References: <49FCA2C9.4060307@videotron.ca> <20090502230627.71ef7124.freebsd@edvax.de> <20090504090804.GA66641@ei.bzerk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 4 May 2009 11:08:04 +0200, Ruben de Groot <mail25@bzerk.org> wrote: > Probably because the # is interpreted as comment. I can reproduce this > in a bourne shell; not in (t)csh. Ah, thank you. According to the prompt, it didn't look like csh in the first place, but not like plain sh, too. Customized bash prompts usually include brackets 'n stuff. Because I'm using csh mostly, I didn't see the problem that "cd #something" == "cd" (which of course leads to $HOME). An attempt to "rm #12345" in sh / bash should lead to an error message (for incomplete rm command). It's safe to use the Midnight Commander to cd into and rm #something files and directories. :-) -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090504204120.31a34cc8.freebsd>