unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 14802-done@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 21:52:26 +0200	[thread overview]
Message-ID: <83ha86u4n9.fsf@gnu.org> (raw)
In-Reply-To: <f7683cbb-1cc2-4dbd-af68-41ce039b539d@default>

> Date: Mon, 10 Feb 2014 11:27:58 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: larsi@gnus.org, 14802@debbugs.gnu.org
> 
> > 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
> 
> So you _are_ saying that "terminal attribute" is a term and concept
> being introduced, and we are not just using the English word
> "attribute" in a general sense.

It's not a term or concept, no.  It's a word.

> In that case, please put it in quotes, as we usually do for a term
> introduction.

It's not a term.

> And, as this bug report requests, say something about what it is, if
> you can - what the term means.  Listing values is not really a
> substitute for that.

Yes, it is.  Because it's not a term.

> > 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"?
> 
> Nothing.  Say what you mean by the term, as we do for each of
> the others you cited.

We don't.

> And index it.

It's not a term, so no need to index it.

> Or follow `i package attribute', to see:
> 
>   Each package (whether simple or multi-file) has certain
>   "attributes":

Which is exactly what we say about terminal attributes.

> (That one is a minimal description - it just introduces particular
> attributes without saying what is meant by the term.  But at least
> it introduces the term explicitly.)

It's not a term.

> BTW, "attributes of text" is in the index, but "text attribute"
> should also be added.

Yes, we should also index "text", and perhaps also "index", because
otherwise who knows what these mean?

> * The term "file attribute" also should be introduced explicitly,
>   in node `File Attributes'.  E.g.:
> 
>     ...detailed information about a file, including the owner and
>     group numbers, the number of names, the inode number, the size,
>     and the times of access and modification.
> 
>   Add something like this: `These characteristics are referred to as
>   "file attributes".'
> 
> * "Process attribute" is also not introduced explicitly, in node
>   `System Processes'.  Also, although function `process-attributes'
>   is indexed, `process attribute' is not.

Like I said: terminal attributes are not special.

Closing, as there's nothing more to be said here, and no bug anywhere
in sight.





  reply	other threads:[~2014-02-10 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<ed6774e8-e43f-45cb-949c-1b792e5a40ab@default>
     [not found] ` <<8361onuej0.fsf@gnu.org>
2014-02-10 19:27   ` bug#14802: 24.3.50; (elisp) Multiple Terminals - what is a terminal attribute? Drew Adams
2014-02-10 19:52     ` Eli Zaretskii [this message]
     [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       ` Drew Adams
2014-02-10 16:18         ` 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=83ha86u4n9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14802-done@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).