unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: karl@freefriends.org (Karl Berry)
Cc: Lute.Kamstra@cwi.nl, bug-texinfo@gnu.org, emacs-devel@gnu.org
Subject: Re: Double hyphens in variable names.
Date: Fri, 3 Oct 2003 21:03:33 -0400	[thread overview]
Message-ID: <200310040103.h9413Xq08288@f7.net> (raw)

    @defvar imenu--index-alist

I propose to make the @def... commands do an implicit @code, more or
less.  The principal change would be the names being printed in
typewriter (and typewriter slanted for arguments, I guess).  We'd get
ligature suppression for free, then.

This seems more logical than the roman fonts (bold and slanted) now
being used, although the roman fonts are prettier and take less space.

Does anyone object to that?

It would also be possible to write special-case code to remove ligatures
and such (in fact I seem to remember doing something along those lines
already for some past bug report), but all in all, the point is that
that identifiers is code, so we should print them in typewriter just
like other code fragments.

k

             reply	other threads:[~2003-10-04  1:03 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04  1:03 Karl Berry [this message]
2003-10-04 22:35 ` Double hyphens in variable names Richard Stallman
2003-10-05  0:53   ` Miles Bader
2003-10-05 10:36     ` Stepan Kasal
2003-10-05  8:34   ` Werner LEMBERG
  -- strict thread matches above, loose matches on Subject: below --
2003-10-07  7:57 David PONCE
2003-10-06  9:26 David PONCE
2003-10-06  9:06 David PONCE
2003-10-06  9:18 ` Lute Kamstra
2003-10-07  5:32 ` Richard Stallman
2003-10-07  6:57   ` Lute Kamstra
2003-10-04  1:03 Karl Berry
2003-10-04  3:51 ` Luc Teirlinck
2003-10-01 13:53 Lute Kamstra
2003-10-02  5:55 ` Eli Zaretskii
2003-10-02  8:43   ` Lute Kamstra
2003-10-02 13:18     ` Luc Teirlinck
2003-10-02 15:11       ` Lute Kamstra
2003-10-02 16:00         ` Luc Teirlinck
2003-10-02 16:14           ` Lute Kamstra
2003-10-02 16:54             ` Andreas Schwab
2003-10-02 17:25             ` Luc Teirlinck
2003-10-03  1:50             ` Luc Teirlinck
2003-10-03  2:13               ` Luc Teirlinck
2003-10-03  3:45                 ` Luc Teirlinck
2003-10-02 19:04         ` Oliver Scholz
2003-10-03  8:39           ` Lute Kamstra
2003-10-03 16:18             ` Luc Teirlinck
2003-10-03 19:37               ` Lute Kamstra
2003-10-03 18:33             ` Luc Teirlinck
2003-10-03 18:42               ` Luc Teirlinck
2003-10-03 19:46               ` Lute Kamstra
2003-10-04 10:47                 ` David Ponce
2003-10-06  7:11                   ` Lute Kamstra
2003-10-06 23:19                 ` Juri Linkov
2003-10-07  9:08                   ` Lute Kamstra
2003-10-03 19:42           ` Richard Stallman
2003-10-03 21:19           ` Juri Linkov
2003-10-02 14:07     ` Luc Teirlinck
2003-10-02 19:15     ` Richard Stallman
2003-10-02 18:56 ` 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=200310040103.h9413Xq08288@f7.net \
    --to=karl@freefriends.org \
    --cc=Lute.Kamstra@cwi.nl \
    --cc=bug-texinfo@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).