unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 66614@debbugs.gnu.org
Subject: bug#66614: 29.1.50; Support not capitalizing words inside symbols
Date: Thu, 19 Oct 2023 18:54:55 +0800	[thread overview]
Message-ID: <87cyxa6fwg.fsf@yahoo.com> (raw)
In-Reply-To: <ierfs274t6t.fsf@janestreet.com> (Spencer Baugh's message of "Wed, 18 Oct 2023 15:38:34 -0400")

Spencer Baugh <sbaugh@janestreet.com> writes:

> +  DEFVAR_BOOL ("case-symbols-as-words", case_symbols_as_words,
> +	       doc: /* If non-nil, case functions treat symbol syntax as part of words.
> +
> +Functions such as `upcase-initials' and `replace-match' check or modify
> +the case pattern of sequences of characters.  Normally, these operate on
> +sequences of characters whose syntax is word constituent.  If this
> +variable is non-nil, then they operate on sequences of characters whose
> +syntax is either word constituent or symbol constituent.
> +
> +This is useful for programming languages and styles where only the first
> +letter of a symbol's name is ever capitalized.*/);
> +  case_symbols_as_words = 0;

Incidentally:

Let's not introduce further instances of the anti-pattern where the
``doc:'' marker in DEFVAR constructs is aligned with its opening paren,
rather than two columns into the word DEFVAR itself.  Generally, this
deprives you of latitude for the first line of the doc string, for you
are either compelled to contravene the 80 column limit or to render that
line exceptionally laconic, both of which are ultimately
counterproductive.

TIA.





  parent reply	other threads:[~2023-10-19 10:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 16:32 bug#66614: 29.1.50; Support not capitalizing words inside symbols Spencer Baugh
2023-10-18 17:01 ` Spencer Baugh
2023-10-18 18:24   ` Eli Zaretskii
2023-10-18 18:55     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-18 18:34   ` Eli Zaretskii
2023-10-18 19:38     ` Spencer Baugh
2023-10-19  4:35       ` Eli Zaretskii
2023-10-21 15:11         ` sbaugh
2023-10-29 11:42           ` Eli Zaretskii
2023-10-19 10:54       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-10-21 15:13         ` sbaugh

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=87cyxa6fwg.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=66614@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=sbaugh@janestreet.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.
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).