From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 14802@debbugs.gnu.org, larsi@gnus.org
Subject: bug#14802: 24.3.50; (elisp) Multiple Terminals - what is a terminal attribute?
Date: Mon, 10 Feb 2014 18:18:59 +0200 [thread overview]
Message-ID: <8361onuej0.fsf@gnu.org> (raw)
In-Reply-To: <ed6774e8-e43f-45cb-949c-1b792e5a40ab@default>
> Date: Sun, 9 Feb 2014 20:03:52 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: larsi@gnus.org, 14802@debbugs.gnu.org
>
> > > What kind of an Emacs thingie is a terminal attribute?
> >
> > It's an attribute of a terminal object.
>
> OK, that gives it a name. Now how about saying what that
> is (in the manual)?
>
> Either that or don't introduce the term - it is just vapor
> otherwise, and confusing. Users can wonder what they're missing,
> and where to find it.
I really don't understand the purpose of this bug report, because this
very node is the answer to all your questions and gripes. It
includes:
. a full list of the attributes of a terminal object (directly below
the single sentence you cited in your report)
. documentation of functions that access those attributes, and
. references to other nodes where related features and issues are
described
What else is missing?
> If the text said "characteristics" or "qualities" or similar,
> users wouldn't wonder so much. But "attribute" typically means
> something particular in software. If what is meant here is the
> ordinary English use of the word then I suggest picking a less
> technical-sounding equivalent.
>
> If what is meant really is something technical that is known
> as a terminal attribute (as one user, I really don't know),
> then that term either needs explaining or users should be
> sent elsewhere for info about it.
I see nothing wrong with the word "attribute". In this very manual,
we have:
. text attributes
. face attributes
. file attributes
. package attributes
. process attributes
What's wrong with having "terminal object attributes"?
next prev parent reply other threads:[~2014-02-10 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<6db9278b-b9e4-4890-ba91-4e2031e3b45f@default>
[not found] ` <<87lhxmyv48.fsf@building.gnus.org>
[not found] ` <<1aaa1446-2f93-457f-af06-a40220ebfe5f@default>
[not found] ` <<83bnyfvdhu.fsf@gnu.org>
2014-02-10 4:03 ` bug#14802: 24.3.50; (elisp) Multiple Terminals - what is a terminal attribute? Drew Adams
2014-02-10 16:18 ` Eli Zaretskii [this message]
[not found] <<ed6774e8-e43f-45cb-949c-1b792e5a40ab@default>
[not found] ` <<8361onuej0.fsf@gnu.org>
2014-02-10 19:27 ` Drew Adams
2014-02-10 19:52 ` Eli Zaretskii
2013-07-05 20:34 Drew Adams
2014-02-08 6:30 ` Lars Ingebrigtsen
2014-02-10 1:27 ` Drew Adams
2014-02-10 2:22 ` Lars Ingebrigtsen
2014-02-10 3:43 ` 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=8361onuej0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14802@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.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).