From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme: hiding certain files in dir windows
Date: Thu, 8 Nov 2001 08:49:51 +0100 [thread overview]
Message-ID: <20011108075001.12879199BB@mail.cse.psu.edu> (raw)
The ignored regexp is global, so I don't need to inherit
it while desdencing the hierarchy.
Of course it would be more powerful to be able to ingore different
patterns on different windows but did not feel the need.
Another comment I have is that perhaps it would be more useful to
have a single `-e' (execute) option for acme instead of the -l and the
-i I have added in my local version for Ignore.
Instead of saying -l mydump -i myregexp
we could just say -e 'Load mydump' -e 'Ignore myregxp',
which would let us execute other various things upon startup.
For example; I'd love this one: acme -e 'acd /dev/sdC1'
I get some spare time for this I may try the experiment; just wanted
to hear comments about it.
next reply other threads:[~2001-11-08 7:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 7:49 Fco.J.Ballesteros [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-08 4:51 rob pike
2001-11-05 8:07 Fco.J.Ballesteros
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=20011108075001.12879199BB@mail.cse.psu.edu \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).