From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Fwd: Bug#711516: zsh-doc: texinfo dir information has leading whitespace
Date: Fri, 7 Jun 2013 15:17:58 +0200 [thread overview]
Message-ID: <20130607131758.GL22106@sym.noone.org> (raw)
Hi,
this has been reported against zsh in Debian at
http://bugs.debian.org/711516
----- Forwarded message from Bruce Stephens <bruce.stephens@isode.com> -----
Date: Fri, 07 Jun 2013 13:13:35 +0100
From: Bruce Stephens <bruce.stephens@isode.com>
Subject: [Pkg-zsh-devel] Bug#711516: zsh-doc: texinfo dir information has
leading whitespace
Package: zsh-doc
Version: 5.0.2-3local1
Severity: normal
Dear Maintainer,
In emacs, I couldn't view the ZSH info. That seems to be the leading
whitespace (different to other dir lines). Removing it seemed to
resolve the problem:
--- zsh-5.0.2.orig/Doc/ztexi.yo
+++ zsh-5.0.2/Doc/ztexi.yo
@@ -71,7 +71,7 @@ def(texinfo)(2)(\
NOTRANS(@ifinfo)+NL()\
NOTRANS(@dircategory Utilities)+NL()\
NOTRANS(@direntry)+NL()\
- NOTRANS( * ZSH: (zsh). The Z Shell Manual.)+NL()\
+ NOTRANS(* ZSH: (zsh). The Z Shell Manual.)+NL()\
NOTRANS(@end direntry)+NL()\
NOTRANS(@end ifinfo)+NL()\
)
[...]
----- End forwarded message -----
I can confirm his findings with GNU Emacs 24.3.1, except that pressing
Enter still yields in Zsh's info page. But in comparison to other
entries, it's neither underlined no highlighted when hovering over it
with the mouse. It just looks like simple text which is surely not
intended.
The patch above should apply against the git HEAD as far as I can see
from http://sourceforge.net/p/zsh/code/ci/master/tree/Doc/ztexi.yo?force=True
Kind regards, Axel
--
/~\ Plain Text Ribbon Campaign | Axel Beckert
\ / Say No to HTML in E-Mail and News | abe@deuxchevaux.org (Mail)
X See http://www.asciiribbon.org/ | abe@noone.org (Mail+Jabber)
/ \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)
reply other threads:[~2013-06-07 13:29 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130607131758.GL22106@sym.noone.org \
--to=abe@deuxchevaux.org \
--cc=zsh-workers@zsh.org \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).