From: "Štěpán Němec" <stepnem@gmail.com>
To: Yuan Fu <casouri@gmail.com>
Cc: 39181@debbugs.gnu.org
Subject: bug#39181: 27.0.50; [PATCH] Allow users to store & restore gdb-mi layout
Date: Mon, 09 Mar 2020 21:54:37 +0100 [thread overview]
Message-ID: <87blp5jlki.fsf@gmail.com> (raw)
In-Reply-To: <150C19DE-ACA2-4066-AB25-DAB7DAD96774@gmail.com>
On Mon, 09 Mar 2020 16:17:59 -0400
Yuan Fu wrote:
>> On Mar 9, 2020, at 3:18 PM, Štěpán Němec <stepnem@gmail.com> wrote:
>>
>>
>> Other than the nit picks below, I have one question: is there any
>> difference between "window layout" and "window configuration" in this
>> context? You seem to be using both interchangeably, both in
>> documentation and the function/variable names. There seems to be some
>> prior usage of "layout" in gdb-mi, but the general Emacs term AFAIK is
>> "configuration". Wouldn't it make sense to unify the usage somewhat, at
>> least in the new code? Just an observation (I found it confusing.)
>>
>
> No, not really, that’s my fault. Before I go in and change every word,
> which one do you think I should use: configuration or layout?
> Configuration is the conventional Emacs term but I felt that layout is
> easier to understand for a user. If you are find with both I guess I
> will change all to configuration.
If they mean the same thing, then I'd say "configuration" is definitely
the way to go.
It is true that some Emacs terms might be unfamiliar to new users, but
thanks to the excellent documentation capabilities it's very easy to
learn the respective definitions (e.g., in this case 'C-h r i
configuration' will display the relevant manual entries). It is
important to stay consistent.
--
Štěpán
next prev parent reply other threads:[~2020-03-09 20:54 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5e950f28.1c69fb81.61726.5731.GMR@mx.google.com>
2020-01-18 20:57 ` bug#39181: 27.0.50; [PATCH] Allow users to store & restore gdb-mi layout Yuan Fu
2020-01-31 10:13 ` Eli Zaretskii
2020-02-02 14:22 ` Yuan Fu
2020-02-07 22:28 ` Yuan Fu
2020-02-10 4:56 ` Yuan Fu
2020-02-15 8:08 ` Eli Zaretskii
2020-02-15 9:55 ` martin rudalics
2020-02-15 10:19 ` Eli Zaretskii
2020-02-15 20:37 ` Yuan Fu
2020-02-16 10:00 ` martin rudalics
2020-03-03 23:41 ` Yuan Fu
2020-03-04 13:28 ` Fu Yuan
2020-03-05 6:12 ` Yuan Fu
2020-03-05 9:14 ` martin rudalics
2020-03-07 18:09 ` Yuan Fu
2020-03-07 19:07 ` Štěpán Němec
2020-03-07 19:17 ` Yuan Fu
2020-03-09 9:01 ` martin rudalics
2020-03-09 17:59 ` Yuan Fu
2020-03-09 19:18 ` Štěpán Němec
2020-03-09 20:17 ` Yuan Fu
2020-03-09 20:54 ` Štěpán Němec [this message]
2020-03-10 8:49 ` martin rudalics
2020-03-10 18:05 ` Fu Yuan
2020-03-11 8:52 ` martin rudalics
2020-03-11 9:26 ` Štěpán Němec
2020-03-12 8:22 ` martin rudalics
2020-03-12 8:49 ` Štěpán Němec
2020-03-12 19:21 ` Yuan Fu
2020-03-13 20:09 ` Yuan Fu
[not found] ` <87lfo4netg.fsf@gmail.com>
2020-03-13 21:13 ` Štěpán Němec
2020-03-13 21:40 ` Yuan Fu
2020-03-13 22:12 ` Štěpán Němec
2020-03-15 15:55 ` martin rudalics
2020-03-16 0:13 ` Yuan Fu
2020-03-16 9:24 ` martin rudalics
2020-03-20 20:03 ` Yuan Fu
2020-03-20 20:58 ` Štěpán Němec
2020-03-21 18:00 ` Yuan Fu
2020-03-21 18:39 ` Štěpán Němec
2020-03-21 21:03 ` Yuan Fu
2020-03-21 21:49 ` Štěpán Němec
2020-03-24 16:14 ` Yuan Fu
2020-03-27 9:01 ` martin rudalics
2020-03-27 16:28 ` Yuan Fu
2020-04-14 8:05 ` martin rudalics
2020-03-10 8:48 ` martin rudalics
2020-04-14 1:17 ` bug#39181: Fwd: Delivery Status Notification (Failure) Yuan Fu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blp5jlki.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=39181@debbugs.gnu.org \
--cc=casouri@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.