unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 40667@debbugs.gnu.org
Subject: bug#40667: 26.3; (1) Emacs manual `i tool bar' (2) `tool-bar-position'
Date: Sat, 25 Apr 2020 13:42:37 +0300	[thread overview]
Message-ID: <834kt7978i.fsf@gnu.org> (raw)
In-Reply-To: <87r1wmt7sv.fsf@tcd.ie> (contovob@tcd.ie)

> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Date: Fri, 17 Apr 2020 17:07:28 +0100
> Cc: 40667@debbugs.gnu.org
> 
> > 2. In node (emacs) `Tool Bars' there is a link to (elisp) `Frame
> > Parameters', for info about parameter `tool-bar-position'.  But that
> > node doesn't present that parameter.  Suggestion: change that link, to
> > point to node `Layout Parameters'.  That's where that parameter is
> > covered.
> 
> It's not just tool-bar-position; the Emacs manual contains at least
> three other references to the supernode '(elisp) Frame Parameters'
> rather than more specific subnodes:

I'm not sure I agree with Drew's suggestion, and therefore with your
suggested changes.  From the context, it seems to me that the intent
is to let the readers understand what the frame parameters are in
general, not to let them read on the specific frame parameter being
discussed (the text there doesn't say anything new for the reader).

> Eli, is this welcome on emacs-27?  Or is it better to xref the supernode
> '(elisp) Frame Parameters' for more context?

I think it's better as it is now, yes.





  reply	other threads:[~2020-04-25 10:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 16:31 bug#40667: 26.3; (1) Emacs manual `i tool bar' (2) `tool-bar-position' Drew Adams
2020-04-17 16:07 ` Basil L. Contovounesios
2020-04-25 10:42   ` Eli Zaretskii [this message]
2020-04-25 11:05     ` Basil L. Contovounesios

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=834kt7978i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=40667@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    /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).