From: peterz@infradead.org
To: yamada.masahiro@socionext.com
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH -v2] scipts/tags.sh: Add custom sort order
Date: Wed, 26 Aug 2020 12:20:17 +0200 [thread overview]
Message-ID: <20200826102017.GT35926@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200806120438.GG35926@hirez.programming.kicks-ass.net>
On Thu, Aug 06, 2020 at 02:04:38PM +0200, peterz@infradead.org wrote:
>
> One long standing annoyance I have with using vim-tags is that our tags
> file is not properly sorted. That is, the sorting exhuberant Ctags does
> is only on the tag itself.
>
> The problem with that is that, for example, the tag 'mutex' appears a
> mere 505 times, 492 of those are structure members. However it is _far_
> more likely that someone wants the struct definition when looking for
> the mutex tag than any of those members. However, due to the nature of
> the sorting, the struct definition will not be first.
>
> So add a script that does a custom sort of the tags file, taking the tag
> kind into account.
>
> The kind ordering is roughly: 'type', 'function', 'macro', 'enum', rest.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
ping?
next prev parent reply other threads:[~2020-08-26 10:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 10:25 [PATCH] scipts/tags.sh: Add custom sort order peterz
2020-08-06 12:04 ` [PATCH -v2] " peterz
2020-08-26 10:20 ` peterz [this message]
2020-09-02 15:58 ` Masahiro Yamada
2020-09-02 16:10 ` Masahiro Yamada
2020-09-02 16:26 ` peterz
2020-09-03 2:07 ` Masahiro Yamada
2020-09-03 7:26 ` peterz
2020-09-04 14:53 ` peterz
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=20200826102017.GT35926@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yamada.masahiro@socionext.com \
/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.
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).