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: 3035@emacsbugs.donarmstrong.com
Subject: bug#3035: 23.0.92; doc, terminology for graphics, display, terminal, etc.
Date: Sat, 18 Apr 2009 13:47:19 +0300	[thread overview]
Message-ID: <83myaei6h4.fsf@gnu.org> (raw)
In-Reply-To: <002301c9bffa$93ba5040$0200a8c0@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Sat, 18 Apr 2009 00:52:08 -0700
> 
> > > 2. In the Elisp manual, I see the use of terms such as "graphical
> > > terminal", "graphicical display" (also "graphics display"),
> > > "(non-)graphics-capable display", "text terminals" (opposed to
> > > graphical), "graphic characters", and "graphical 
> > > attributes", without any real explanation or definition.
> > 
> > From the node "Frames", near the beginning:
> > 
> >        There are two classes of terminals: text-only terminals and
> >     graphical terminals.  Text-only terminals are non-graphics-capable
> >     display devices, including "terminal emulators" such as xterm.  On
> >     text-only terminals, each frame occupies the entire 
> >     terminal screen;
> >     although you can create additional frames and switch 
> >     between them, only
> >     one frame can be shown at any given time.  We refer to frames on
> >     text-only terminals as "terminal frames".  Graphical 
> >     terminals, on the
> >     other hand, are graphics-capable windowing systems, such as the X
> >     Window System.  On a graphical terminal, Emacs can 
> >     display multiple
> >     frames simultaneously.  We refer to such frames as 
> >     "window frames".
> > 
> > If this is not good enough, please tell what is missing.
> 
> Yes, that helps wrt "graphical terminal" and "text terminal" (but not with the
> rest).

But that's what your Item 2 (above) was all about: the distinction
between text and graphical terminals.  What else is needed?

> (BTW, in my version, it says "On these "multi-monitor" setups, a single DISPLAY
> value controls the output to all the physical monitors.")

My citation was from today's CVS.

> BTW, I see in passing this, in node Multiple Displays: "_the_ selected frame".
> Is it normal that those underscores are shown as such? 

That's how emphasis is shown in Info.  In print, it comes out in
slanted typeface.

> > They are not.  Each one should be explained in its own place, and the
> > more important ones, although certainly not all, are in the Glossary
> > node.
> 
> I see. That's good.
> 
> How do I get to the Glossary node? I tried `g Glossary' and got no match. I
> tried `C-h m' and `?' and looked for "Glossary" in the Info mode help and
> summary, but didn't find it in either.

Sorry, I mean the Glossary in the Emacs manual, not in ELisp.






  reply	other threads:[~2009-04-18 10:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 16:46 bug#3035: 23.0.92; doc, terminology for graphics, display, terminal, etc Drew Adams
2009-04-18  7:16 ` Eli Zaretskii
2009-04-18  7:52   ` Drew Adams
2009-04-18 10:47     ` Eli Zaretskii [this message]
2009-04-18 16:23       ` Drew Adams
2009-04-18 17:20         ` Eli Zaretskii
2009-04-18 17:29           ` Drew Adams
2009-04-18 20:55             ` Eli Zaretskii
2009-04-18 21:18               ` Drew Adams
2009-04-19  3:17                 ` Stefan Monnier
2009-04-19  5:01                   ` Drew Adams
2009-04-19 18:09                     ` Stefan Monnier
2009-04-19 19:33                       ` Drew Adams
2009-04-20 16:24                         ` Stefan Monnier
2011-07-11 14:29                           ` Lars Magne Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
2009-04-18  1:50 Chong Yidong
2009-04-18  2:03 ` Drew Adams
2009-04-18  6:26   ` Eli Zaretskii
2009-04-18  7:17     ` Drew Adams
2009-04-18 10:39       ` Eli Zaretskii
2009-04-18 16:23         ` Drew Adams
2009-04-18 13:41   ` Chong Yidong

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=83myaei6h4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=3035@emacsbugs.donarmstrong.com \
    --cc=drew.adams@oracle.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).