emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#31567: closed (emacs-lisp-intro.pdf - two undefine


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#31567: closed (emacs-lisp-intro.pdf - two undefined items - page 1 (PDF viewer page 17 of 271))
Date: Wed, 23 May 2018 16:36:01 +0000

Your message dated Wed, 23 May 2018 19:35:26 +0300
with message-id <address@hidden>
and subject line Re: bug#31567: Acknowledgement (emacs-lisp-intro.pdf - two 
undefined items - page 1 (PDF viewer page 17 of 271))
has caused the debbugs.gnu.org bug report #31567,
regarding emacs-lisp-intro.pdf - two undefined items - page 1 (PDF viewer page 
17 of 271)
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
31567: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31567
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: emacs-lisp-intro.pdf - two undefined items - page 1 (PDF viewer page 17 of 271) Date: Wed, 23 May 2018 20:30:20 +1000
Hello.

The footnote as follows

  #+BEGIN_EXAMPLE
    1 A single-quote is an abbreviation for the special form quote; you need 
not think about special forms now. See ⟨unde ned⟩ “Complications”, page ⟨unde 
ned⟩.
  #+END_EXAMPLE 

is produced from line 1009 in emacs-lisp-intro.texi as follows

: about special forms now.  @xref{Complications}.}  Lists are the basis

using `make docs’ for release `tags/emacs-26.1-rc1’. 

I expect the `⟨undefined⟩' to be filled and function to jump to places.



Note, the example copy is missing `fi’ in `undefined' possibly due to the lack 
of font in this email application.


--- End Message ---
--- Begin Message --- Subject: Re: bug#31567: Acknowledgement (emacs-lisp-intro.pdf - two undefined items - page 1 (PDF viewer page 17 of 271)) Date: Wed, 23 May 2018 19:35:26 +0300
> From: Van L <address@hidden>
> Date: Wed, 23 May 2018 21:23:31 +1000
> 
> address@hidden has no target in at `tex’ context.

Yes, someone made this section be a node only in the on-line versions,
but forgot to review all the cross-references to it.  There were a
couple more like that in the manual.

> Maybe it needs to read address@hidden @xref{Complications} @end ifnottex’.

No, that's too radical.  I simply fixed the cross-references to work
in the printed version of the manual as well.

Thanks.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]