From: Brian Elmegaard <brian@rkspeed-rugby.dk>
Subject: Re: Is buffer size fixed in batch mode?
Date: 03 Dec 2005 11:28:28 +0100 [thread overview]
Message-ID: <uoe3yjwz7.fsf@rkspeed-rugby.dk> (raw)
In-Reply-To: mailman.17722.1133580378.20277.help-gnu-emacs@gnu.org
Ian Zimmerman <nobrowser@gmail.com> writes:
> Please fix the grammar here first; the sense is lost.
Oops, sorry.
The question is: What differences should or could be expected when
interactively loading and running a lisp function compared to a call
like:
emacs foo.bar -l baz.el -f baz
--
Brian (remove the sport for mail)
http://www.et.web.mek.dtu.dk/Staff/be/be.html
http://www.rugbyklubben-speed.dk
next prev parent reply other threads:[~2005-12-03 10:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 10:37 Is buffer size fixed in batch mode? Brian Elmegaard
2005-12-03 3:26 ` Ian Zimmerman
[not found] ` <mailman.17722.1133580378.20277.help-gnu-emacs@gnu.org>
2005-12-03 10:28 ` Brian Elmegaard [this message]
2005-12-03 14:32 ` Johan Bockgård
2005-12-07 7:53 ` Brian Elmegaard
2005-12-07 9:39 ` David Kastrup
2005-12-07 9:44 ` Brian Elmegaard
2005-12-07 10:21 ` David Kastrup
2005-12-07 10:32 ` Brian Elmegaard
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=uoe3yjwz7.fsf@rkspeed-rugby.dk \
--to=brian@rkspeed-rugby.dk \
/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).