From: Pavel Machek <pavel@ucw.cz>
To: Anton Altaparmakov <aia21@cus.cam.ac.uk>
Cc: Nerijus Baliunas <nerijus@users.sourceforge.net>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ntfs-dev@lists.sourceforge.net"
<linux-ntfs-dev@lists.sourceforge.net>,
Padraig Brady <padraig@antefacto.com>
Subject: Re: Re[2]: ANN: NTFS 2.0.1 for kernel 2.5.7 released
Date: Wed, 3 Apr 2002 09:32:10 +0200 [thread overview]
Message-ID: <20020403073209.GA1474@elf.ucw.cz> (raw)
In-Reply-To: <ISPFE11z1aiG4HHZM9I000037fa@mail.takas.lt> <Pine.SOL.3.96.1020329134328.18653B-100000@virgo.cus.cam.ac.uk>
Hi!
> > AA> > To have all files executable breaks stuff like:
> > AA> > midnight commander (won't open executable files)
> > AA>
> > AA> Ouch, that is plain stupid... mc should be fixed. I open executables all
> > AA> the time and mc should automatically fire up a hexeditor.
> >
> > You probably misunderstood the problem - I cannot enter archive files (.tgz, .zip)
> > in mc if these files are marked as executable - mc just tries to execute them.
>
> Ah, that is a bad thing. (I don't use mc as you may have guessed...)
Well, not completely true. Let's see.
When you press enter, mc does default action. Default action is
execute, if file is executable
open tar gz archive, if file is named *.tgz
etc. It is actually quite reasonable. If you want to open executable
.tgz archive just do cd foo.tgz#utar.
Pavel
--
(about SSSCA) "I don't say this lightly. However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
next prev parent reply other threads:[~2002-04-03 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ISPFE11z1aiG4HHZM9I000037fa@mail.takas.lt>
2002-03-29 13:56 ` Re[2]: ANN: NTFS 2.0.1 for kernel 2.5.7 released Anton Altaparmakov
2002-04-03 7:32 ` Pavel Machek [this message]
2002-03-29 12:57 Anton Altaparmakov
2002-03-29 13:24 ` Re[2]: " Nerijus Baliunas
2002-03-30 10:34 ` Joachim Breuer
2002-03-30 11:02 ` Nicholas Miell
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=20020403073209.GA1474@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=aia21@cus.cam.ac.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=nerijus@users.sourceforge.net \
--cc=padraig@antefacto.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox