From: Kevin Ryde <user42@zip.com.au>
Subject: manual xrefs widget.texi and frames.texi
Date: Thu, 19 May 2005 08:46:30 +1000 [thread overview]
Message-ID: <87zmusw3sp.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
I spotted a couple of cross references between manuals that need
updating for recent node renamings,
In man,
2005-05-17 Kevin Ryde <user42@zip.com.au>
* widget.texi (Basic Types): Update cross ref from "Enabling Mouse-1
to Follow Links" to "Links and Mouse-1" per recent lispref/text.texi
change.
In lispref,
* frames.texi (Initial Parameters): Update of Emacs Invocation cross
reference.
[-- Attachment #2: widget.texi.mouse1.diff --]
[-- Type: text/plain, Size: 655 bytes --]
*** widget.texi.~1.28.~ 2005-01-19 10:24:42.000000000 +1100
--- widget.texi 2005-05-17 15:29:41.218747592 +1000
***************
*** 596,602 ****
@vindex follow-link@r{ keyword}
@item :follow-link
Specifies how to interpret a @key{mouse-1} click on the widget.
! @xref{Enabling Mouse-1 to Follow Links,,, elisp, the Emacs Lisp Reference Manual}.
@vindex indent@r{ keyword}
@item :indent
--- 596,602 ----
@vindex follow-link@r{ keyword}
@item :follow-link
Specifies how to interpret a @key{mouse-1} click on the widget.
! @xref{Links and Mouse-1,,, elisp, the Emacs Lisp Reference Manual}.
@vindex indent@r{ keyword}
@item :indent
[-- Attachment #3: frames.texi.invoc.diff --]
[-- Type: text/plain, Size: 985 bytes --]
*** frames.texi.~1.87.~ 2005-05-17 09:14:20.000000000 +1000
--- frames.texi 2005-05-17 15:39:17.851086152 +1000
***************
*** 304,311 ****
If you use options that specify window appearance when you invoke Emacs,
they take effect by adding elements to @code{default-frame-alist}. One
exception is @samp{-geometry}, which adds the specified position to
! @code{initial-frame-alist} instead. @xref{Command Arguments,,, emacs,
! The GNU Emacs Manual}.
@node Window Frame Parameters
@subsection Window Frame Parameters
--- 304,311 ----
If you use options that specify window appearance when you invoke Emacs,
they take effect by adding elements to @code{default-frame-alist}. One
exception is @samp{-geometry}, which adds the specified position to
! @code{initial-frame-alist} instead. @xref{Emacs Invocation,, Command
! Line Arguments for Emacs Invocation, emacs, The GNU Emacs Manual}.
@node Window Frame Parameters
@subsection Window Frame Parameters
[-- Attachment #4: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
reply other threads:[~2005-05-18 22:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87zmusw3sp.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).