From: Bart Schaefer <schaefer@brasslantern.com>
To: Baptiste Daroussin <baptiste.daroussin@gmail.com>
Cc: Zsh workers <zsh-workers@zsh.org>
Subject: Re: Fix zshmodule.1 syntax
Date: Sat, 22 Nov 2014 14:28:13 -0800 [thread overview]
Message-ID: <141122142813.ZM15188@torch.brasslantern.com> (raw)
In-Reply-To: <CAPKC6oKA-MENb17S_T-Rn0Yy2guw7+p=-h5yGFEFCNPCUDkzWw@mail.gmail.com>
On Nov 22, 1:26pm, Baptiste Daroussin wrote:
} Subject: Re: Fix zshmodule.1 syntax
}
} 2014-11-22 7:07 GMT+01:00 Bart Schaefer <schaefer@brasslantern.com>:
} > On Nov 21, 11:06pm, Baptiste Daroussin wrote:
} > }
} > } Using mandoc -Tlint -Werror on the generated zshmodule.1 showed a
} > } syntax error the following patch fixes it:
} > }
} > } https://people.freebsd.org/~bapt/0001-Do-not-close-twice-the-index.patch
} >
} > Thanks, but this can't be all there is to it. There are two startitem()
} > calls, so there need to be two enditem() calls.
}
} The startitem() is closed 2 lines after
Hmm.
8 lines matching "\\(start\\|end\\)item" in buffer mod_system.yo.
9:startitem()
63:startitem()
89:enditem()
161:enditem()
165:startitem()
181:startitem()
191:enditem()
193:enditem()
Your diff would remove the enditem() at line 191, leaving line 181 with
no matching end. I can believe the generated manual page is wrong, but
the yodl source is not as far as I can tell.
Looking at zshmodules.1 from my latest build I see:
sysparams
A readonly associative array. The keys are:
pid Returns the process ID of the current process, even in sub-
shells. Compare $$, which returns the process ID of the main
shell process.
ppid Returns the process ID of the parent of the current process,
even in subshells. Compare $PPID, which returns the process ID
of the parent of the main shell process.
Here "pid" and "ppid" are meant to be indented an extra level, but
are not. The nesting works in zle.yo -> zshzle.1 for bindkey:
bindkey [ options ] [ in-string ]
bindkey's options can be divided into three categories: keymap
selection for the current command, operation selection, and
others. The keymap selection options are:
-e Selects keymap 'emacs' for any operations by the current
command, and also links 'emacs' to 'main' so that it is
selected by default the next time the editor starts.
So there's something subtle going on in mod_system.yo.
next prev parent reply other threads:[~2014-11-22 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 22:06 Baptiste Daroussin
[not found] ` <141121220737.ZM13875@torch.brasslantern.com>
2014-11-22 12:26 ` Baptiste Daroussin
2014-11-22 22:28 ` Bart Schaefer [this message]
2014-11-22 22:45 ` Bart Schaefer
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=141122142813.ZM15188@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=baptiste.daroussin@gmail.com \
--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).