From: Sebastian Luque <spluque@gmail.com>
Subject: Re: editing large files
Date: Sat, 22 Oct 2005 11:56:18 -0500 [thread overview]
Message-ID: <87irvp4hjh.fsf@gmail.com> (raw)
In-Reply-To: 877jc5oq7r.fsf@tiger.rapttech.com.au
Tim X <timx@spamto.devnul.com> wrote:
[...]
> For large files, I usually just split them up, do my editing and then
> join them back together again. If the changes I need to make are
> repetitive or fairly easily specified in a programatic fashion, I just
> use sed.
Thanks to all of you for your suggestions. Indeed, I ended up using AWK,
since they were all comma-delimited files (tables).
Cheers,
--
Sebastian P. Luque
next prev parent reply other threads:[~2005-10-22 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12184.1129935330.20277.help-gnu-emacs@gnu.org>
2005-10-21 23:23 ` editing large files Pascal Bourguignon
2005-10-22 7:38 ` David Kastrup
2005-10-22 9:28 ` Tim X
2005-10-22 16:56 ` Sebastian Luque [this message]
[not found] ` <mailman.12242.1130000339.20277.help-gnu-emacs@gnu.org>
2005-10-23 5:36 ` Indenting in HTML mode Tyler
2005-10-24 11:59 ` Anselm Helbig
2005-10-21 22:53 editing large files Sebastian Luque
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=87irvp4hjh.fsf@gmail.com \
--to=spluque@gmail.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).