unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Barry Margolin <barmar@genuity.net>
Subject: Re: garbace collection of point-markers
Date: Fri, 31 Jan 2003 20:17:18 GMT	[thread overview]
Message-ID: <iRA_9.26$is4.1335@paloalto-snr1.gtei.net> (raw)
In-Reply-To: 87vg05yu6h.fsf@thalassa.informatimago.com

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]

In article <87vg05yu6h.fsf@thalassa.informatimago.com>,
Pascal Bourguignon  <pjb@informatimago.com> wrote:
>kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> Pascal Bourguignon <pjb@informatimago.com> writes:
>> 
>> > Note that in emacs, the reader does not
>> > convert-case the symbols.  So (not (eq 'DONT-COPY-P 'dont-copy-p))
>> 
>> It seems customary to refer to the args of a function by uppercase
>> names.  Type C-h f kill-buffer RET for an example.
>
>Exact.  But as a typographical distinction. Now that we have bolds and
>italics and  fonts, perhaps they should  just be put in  bold and stay
>low case.  When  you work with Common-Lisp in  addition to emacs lisp,
>it's usefull to keep the distinction in mind.

Perhaps in Emacs documentation, but in Usenet you should limit yourself to
simple ASCII.

-- 
Barry Margolin, barmar@genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.

  reply	other threads:[~2003-01-31 20:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-31  8:49 garbace collection of point-markers Stefan Kamphausen
2003-01-31 10:10 ` Pascal Bourguignon
2003-01-31 15:18   ` Kai Großjohann
2003-01-31 19:51     ` Pascal Bourguignon
2003-01-31 20:17       ` Barry Margolin [this message]
2003-02-01  4:00         ` Pascal Bourguignon
2003-01-31 16:13   ` Barry Margolin
2003-01-31 17:21     ` Stefan Monnier <foo@acm.com>
2003-02-03 18:04       ` Stefan Kamphausen
2003-01-31 19:02 ` 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='iRA_9.26$is4.1335@paloalto-snr1.gtei.net' \
    --to=barmar@genuity.net \
    /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).