From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: dana <dana@dana.is>
Cc: Zsh workers <zsh-workers@zsh.org>
Subject: Re: [PATCH] Completion: Improve _man (3)
Date: Fri, 15 Jun 2018 14:47:12 +0000 [thread overview]
Message-ID: <20180615144712.zh3ld5aan5r2va3s@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <64E31285-3F41-4F38-8E70-A42F2F2735AD@dana.is>
dana wrote on Fri, Jun 15, 2018 at 09:21:07 -0500:
> On 15 Jun 2018, at 09:05, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> >Thanks for the quick turnaround. With this patch, `man 3 utf<TAB>`,
> >`man 3per utf<TAB>`, and `man 3perll utf<TAB>` all complete to
> >`... utf8`. That's correct for the first two but wrong for the last one:
>
> Oops, i confused myself looking at the old one. Fixing that actually improves
> the partial matching a lot in general, thanks. Try this, if you don't mind.
Much better, thanks.
While here, I noticed this:
[[[
% zstyle \* group-name ''
% zstyle \* format '> %d'
% zstyle \* separate-sections true
% man ut
> manual page, section 2 (system calls)
utime utimensat
> manual page, section 3 (library functions)
utf8 utime
> manual page, section 7 (miscellanea)
utf-8 utf8 utime.h utmpx.h
]]]
This lists utime(2), utime(3), utf8(3perl), utf8(7), and utime.h(7posix), among
others. Should there be separate groups for each section, i.e., one group for
each of (2 3 3perl 7 7posix)? (This is orthogonal to dana's patch.)
Cheers,
Daniel
prev parent reply other threads:[~2018-06-15 14:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 6:06 [PATCH] Completion: Improve _man dana
2018-06-10 13:07 ` Oliver Kiddle
2018-06-10 14:02 ` dana
2018-06-11 10:48 ` [PATCH] Completion: Improve _man (2) dana
2018-06-14 9:50 ` Daniel Shahaf
2018-06-14 10:20 ` dana
2018-06-15 13:59 ` [PATCH] Completion: Improve _man (3) dana
2018-06-15 14:05 ` Daniel Shahaf
2018-06-15 14:21 ` dana
2018-06-15 14:39 ` Mikael Magnusson
2018-06-15 14:55 ` Daniel Shahaf
2018-06-15 15:14 ` dana
2018-06-15 15:36 ` Peter Stephenson
2018-06-15 17:27 ` Mikael Magnusson
2018-06-15 14:47 ` Daniel Shahaf [this message]
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=20180615144712.zh3ld5aan5r2va3s@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=dana@dana.is \
--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).