From: Fu Yuan <casouri@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: "Štěpán Němec" <stepnem@gmail.com>, 39181@debbugs.gnu.org
Subject: bug#39181: 27.0.50; [PATCH] Allow users to store & restore gdb-mi layout
Date: Tue, 10 Mar 2020 14:05:56 -0400 [thread overview]
Message-ID: <91E91E25-9956-4D10-BD99-DC028156731C@gmail.com> (raw)
In-Reply-To: <fd22a9e9-692d-f459-1770-07c41a98a1e4@gmx.at>
Hmmm, so what is the best approach here? Use layout in button names (in the menu bar) and configuration everywhere else? And maybe mention the equivalence between layout and configuration in help echo?
Yuan
> 在 2020年3月10日，上午4:49，martin rudalics <rudalics@gmx.at> 写道：
>
> > 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.
>
> While I agree with Štěpán that we should use a unified nomenclature
> wherever possible, most GDB users will probably prefer "layout" here.
>
> martin
>
next prev parent reply other threads:[~2020-03-10 18:05 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
2020-03-10 8:49 ` martin rudalics
2020-03-10 18:05 ` Fu Yuan [this message]
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
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=91E91E25-9956-4D10-BD99-DC028156731C@gmail.com \
--to=casouri@gmail.com \
--cc=39181@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=stepnem@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 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).