| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
| |
To make -tu work correctly, which doesn't have the word-boundary
constraint.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
|
| |
In some cases it might be nice, but in some other cases, it might
cause a lot of code to be printed. Let the user explicitly search
for it or not in a separate run.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Avoid this glich from glibc:
./sysdeps/unix/sysv/linux/x86/sys/ucontext.h:133:
typedef struct
{
gregset_t __ctx(gregs);
/* Note that fpregs is a pointer. */
fpregset_t __ctx(fpregs);
__extension__ unsigned long long __reserved1 [8];
} mcontext_t;
/* Userlevel context. */
typedef struct ucontext_t
{
unsigned long int __ctx(uc_flags);
struct ucontext_t *uc_link;
stack_t uc_stack;
mcontext_t uc_mcontext;
sigset_t uc_sigmask;
struct _libc_fpstate __fpregs_mem;
__extension__ unsigned long long int __ssp[4];
} ucontext_t;
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
| |
- Typedefs to arrays of structures.
- Typedefs to structures of the same name.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
|
| |
- Use the same ammount of spaces for the closing brace as for the
opening brace.
- Fix position of attributes.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
| |
SC2068: Double quote array expansions to avoid re-splitting elements.
Reported-by: shellcheck(1)
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
| |
SC2124: Use $* instead of $@ to concatenate.
Reported-by: shellcheck(1)
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
| |
SC2004: $/${} is unnecessary on arithmetic variables.
Reported-by: shellcheck(1)
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
| |
Also, add some symmetry between ${iflag} and ${lflag}.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Normally, one either wants to see a declaration/definition, or its
uses, but not both at the same time. Also, there are usually many
more use sites than than definitions, and therefore definitions
are shadowed between all the noise. Restrict the default to
declarations and definitions, which in my experience seems to be
the most common use case.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
When it calls grepc_type_struct_union_enum(), it needs to use a
different file list, since it's searching for an identifier
different from the one passed in the command line.
Also, while at it, improve the quoting of the pattern passed to
pcregrep(1).
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
| |
Sort alphabetically the optstring.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
| |
Rename functions to have different starting letters. Also rename
the macro functions to more closely match ISO C nomenclature.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
| |
Most importantly, typedef enum.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
| |
Reported-by: наб <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
| |
Use alphabetic order.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
| |
Improve grouping so that adding flags for running the different
functions is simple.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
| |
Also, update the manual page EXAMPLES regarding blank lines.
Reported-by: наб <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
| |
Reported-by: наб <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using caps instead of <> will be nicer when we add options and
optional arguments for the files/directories:
Usage: grepc [OPTION]... IDENTIFIER [FILE]...
vs
Usage: grepc [<option>]... IDENTIFIER [<file>]...
Also, it's what pcregrep(1) and GNU grep(1) use, so it's good to
use the same syntax here.
Reported-by: наб <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
| |
Reported-by: наб <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
| |
Let's fall on the safe side.
Reported-by: наб <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
| |
Reported-by: наб <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
| |
Reported-by: наб <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
| |
Reported-by: наб <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
| |
This improves the readability of the regex, and also the
robustness, at the cost of just a few ms.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
Instead of running find and grep -l for every function, store the
result in a temporary file for reuse in all functions.
This is a considerable speedup, between 3x and 10x in some tests
within the Linux kernel source code.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
|
| |
Those two spaces are for handling some insane GNU style. Those
are always spaces, so let's use ' ' instead of '\s\s' to make
sure we don't match two tabs, or things like that.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
| |
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|
|
|
|
|
|
|
|
| |
Use 2 grep(1) filters instead of 1, to be able to filter better
before the multiline pcregrep(1) filter, which is considerably
slower.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
|