From: Sam Steingold <sds@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 52785@debbugs.gnu.org
Subject: bug#52785: 29.0.50; user-full-name: "Chop off everything after the first comma"
Date: Fri, 24 Dec 2021 15:04:38 -0500 [thread overview]
Message-ID: <lzczllvkfd.fsf@3c22fb11fdab.ant.amazon.com> (raw)
In-Reply-To: <8335mhsrv3.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 24 Dec 2021 21:52:16 +0200")
> * Eli Zaretskii <ryvm@tah.bet> [2021-12-24 21:52:16 +0200]:
>
>> From: Sam Steingold <sds@gnu.org>
>> Date: Fri, 24 Dec 2021 14:35:00 -0500
>>
>> --8<---------------cut here---------------start------------->8---
>> /* Chop off everything after the first comma. */
>> q = strchr (p, ',');
>> full = make_string (p, q ? q - p : strlen (p));
>> --8<---------------cut here---------------end--------------->8---
>>
>> The result is that when full name is specified in the system as
>> "Steingold, Sam", `user-full-name' returns "Steingold".
>>
>> Are we really sure that this is still the intended behavior?
>
> Yes, I think so.
Why?
>> If yes, we might want to document it in the doc string and info.
>
> Feel free to suggest a documentation patch.
Sure, as soon as I understand the reason for this behavior (because it
has to be included in the doc!)
--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.2022
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://ij.org/ https://ffii.org https://mideasttruth.com
Daddy, why doesn't this magnet pick up this floppy disk?
next prev parent reply other threads:[~2021-12-24 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 19:35 bug#52785: 29.0.50; user-full-name: "Chop off everything after the first comma" Sam Steingold
2021-12-24 19:52 ` Eli Zaretskii
2021-12-24 20:04 ` Sam Steingold [this message]
2021-12-24 20:22 ` Andreas Schwab
2021-12-25 7:39 ` Eli Zaretskii
2021-12-24 20:22 ` Eli Zaretskii
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=lzczllvkfd.fsf@3c22fb11fdab.ant.amazon.com \
--to=sds@gnu.org \
--cc=52785@debbugs.gnu.org \
--cc=eliz@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).