From: Michael M Mason <mmmason@ntlworld.com>
Subject: Re: Output in Emacs
Date: Sat, 08 Nov 2003 00:00:17 +0000 [thread overview]
Message-ID: <cfcoqvckoojlqfq67a1luuagikf2se37su@4ax.com> (raw)
In-Reply-To: m3n0b9nqbw.fsf@mika.informatik.uni-freiburg.de
On 06 Nov 2003 22:24:03 +0100, LEE Sau Dan
<danlee@informatik.uni-freiburg.de> wrote:
>>>>>> "Edi" == Edi Weitz <edi@agharta.de> writes:
>
> Edi> You should adhere to the usual conventions for intending Lisp
>........................................................^^^^^^^^^
> Edi> code. This'll help other people to read it.
>
>"indenting", not "intending". :)
...unless you're using the *Scratch* buffer...
--
Michael
next prev parent reply other threads:[~2003-11-08 0:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 19:15 Output in Emacs Dirk Joos
2003-11-02 19:26 ` Edi Weitz
2003-11-03 22:01 ` Johannes Quint
2003-11-06 21:24 ` LEE Sau Dan
2003-11-08 0:00 ` Michael M Mason [this message]
2003-11-02 19:32 ` Edward Dodge
[not found] <mailman.3057.1067896989.21628.help-gnu-emacs@gnu.org>
2003-11-03 22:25 ` Barry Margolin
2003-11-03 23:36 ` Johan Bockgård
2003-11-03 23:38 ` Kevin Rodgers
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=cfcoqvckoojlqfq67a1luuagikf2se37su@4ax.com \
--to=mmmason@ntlworld.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).