From: "Roodwriter@core.com" <Roodwriter@core.com>
Subject: Re: Emacs as a command line tool
Date: Thu, 19 Feb 2004 02:01:37 -0500 [thread overview]
Message-ID: <1038no01tm8n0e9@corp.supernews.com> (raw)
In-Reply-To: c0svh8$irc$2@news.net.uni-c.dk
David Rasmussen wrote:
> Joakim Hove wrote:
>>
>> how about redirection:
>>
>> expand file > tmp_file ; mv tmp_file file
>>
>
> Sure, but that doesn't solve the problem with batch runs. I can't do
>
> expand *.cpp
>
> which would have been very easy.
>
> /David
It just occurred to me (when I was thinking of something else, oddly) an
easy way to solve your problem--at least for me.
Make a macro.
First, use the dired function to set up the directory with all these files.
Make sure they're set as whole lines. Then start the macro recording
function.
Search for the cpp extension, stop the search, hit <return> to call the file
up, untabify the file, save it, close it, returning to dired. End the
macro.
Now all you have to do is tell the macro to repeat the required number of
times.
--Rod
__________
Author of "Linux for Non-Geeks--Clear-eyed Answered for Practical Consumers"
and "Boring Stories from Uncle Rod." Both are available at
http://www.rodwriterpublishing.com/index.html
To reply by e-mail, take the extra "o" out of the name.
next prev parent reply other threads:[~2004-02-19 7:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 10:54 Emacs as a command line tool David Rasmussen
2004-02-17 10:57 ` Billy O'Connor
2004-02-17 11:08 ` David Rasmussen
2004-02-17 15:16 ` Pascal Bourguignon
2004-02-17 16:02 ` David Rasmussen
2004-02-17 17:06 ` Pascal Bourguignon
2004-02-19 0:29 ` Kevin Rodgers
2004-02-17 11:14 ` Roodwriter
2004-02-17 11:19 ` David Rasmussen
2004-02-17 11:46 ` Joakim Hove
2004-02-17 12:06 ` David Rasmussen
2004-02-17 13:20 ` expand tabs in a shell Bruce Ingalls
2004-02-17 17:24 ` Bruce Ingalls
2004-02-19 7:01 ` Roodwriter [this message]
2004-02-17 13:35 ` Emacs as a command line tool Floyd Davidson
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=1038no01tm8n0e9@corp.supernews.com \
--to=roodwriter@core.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).