unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 13473@debbugs.gnu.org
Subject: bug#13473: 24.3.50; Display Tables doc bug
Date: Wed, 14 Feb 2018 14:33:18 +0100	[thread overview]
Message-ID: <87inazk869.fsf@gmx.net> (raw)
In-Reply-To: <878tbw9xn2.fsf@users.sourceforge.net> (Noam Postavsky's message of "Tue, 13 Feb 2018 20:18:41 -0500")

On Tue, 13 Feb 2018 20:18:41 -0500 Noam Postavsky <npostavs@users.sourceforge.net> wrote:

> Stephen Berman <stephen.berman@gmx.net> writes:
>
>>   The glyph used to draw the border between side-by-side windows (the
>>   default is @samp{|}).  @xref{Splitting Windows}.  This takes effect only
>>   when there are no scroll bars; if scroll bars are supported and in use,
>> ! a scroll bar separates the two windows.  On graphical terminals, Emacs
>> ! uses a thin line to indicate the border, so the display table has no
>> ! effect.
>>   @end table
>
> If it's only effective on a tty display, then is the scroll bar
> reference irrelevant?  AFAIK, there are never scroll bars on a tty
> display anyway.

I think that's right, so the above is misleading (with or without the
change).  I guess it's sufficient just to say "On graphical terminals,
this has no effect."[1] But maybe it would be helpful to say why it has
no effect (even though you see it when you use a graphical display):

diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi
index fbf943a08c..81084d7c06 100644
--- a/doc/lispref/display.texi
+++ b/doc/lispref/display.texi
@@ -6988,9 +6988,10 @@ Display Tables
 
 @item 5
 The glyph used to draw the border between side-by-side windows (the
-default is @samp{|}).  @xref{Splitting Windows}.  This takes effect only
-when there are no scroll bars; if scroll bars are supported and in use,
-a scroll bar separates the two windows.
+default is @samp{|}).  @xref{Splitting Windows}.  On graphical
+terminals, this has no effect: if scroll bars are in use, a scroll bar
+separates the two windows, and if scroll bars are not in use, the
+border is a thin unbroken line.
 @end table
 
   For example, here is how to construct a display table that mimics

Steve Berman

Footnotes:
[1]  At least not on GTK+ builds.  Someone should check other toolkits
     and non-toolkit builds (I currently can't readily do that), though
     it seems unlikely they would differ on this.






  reply	other threads:[~2018-02-14 13:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 11:10 bug#13473: 24.3.50; Display Tables doc bug Stephen Berman
2018-02-14  1:18 ` Noam Postavsky
2018-02-14 13:33   ` Stephen Berman [this message]
2018-02-14 16:05     ` martin rudalics
2018-02-14 18:29       ` Eli Zaretskii
2018-02-14 18:06     ` Eli Zaretskii
2018-02-14 18:33       ` Stephen Berman
2019-10-11  2:08 ` Stefan Kangas

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=87inazk869.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=13473@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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).