[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Should diff.elisp.xfuncname match cl-lib macros?
From: |
Basil L. Contovounesios |
Subject: |
Re: Should diff.elisp.xfuncname match cl-lib macros? |
Date: |
Sat, 16 Mar 2019 21:55:15 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Stefan Monnier <address@hidden> writes:
>>> AFAIK xfuncname is mostly used to add the "containing function name"
>>> on the header of each diff hunk.
>> That's a million times less important to me than "git log -L".
>
> Indeed, it's not an important feature at all. It's just a nice "frill".
>
> Given the inevitable unreliability of the info it gets, I'm surprised it
> grew to take a more significant role in -L. I guess it's still
> worthwhile in the sense that it's good when it works and when it doesn't
> you're no worse off than if you didn't have that feature.
I agree, FWIW. My main use for xfuncname is as a manual alternative to
add-change-log-entry, by using diff hunk headers to know where a change
has been made. When searching Git logs I tend to use --grep or -G
rather than -L.
--
Basil
- Should diff.elisp.xfuncname match cl-lib macros?, Basil L. Contovounesios, 2019/03/15
- Re: Should diff.elisp.xfuncname match cl-lib macros?, Basil L. Contovounesios, 2019/03/16
- Re: Should diff.elisp.xfuncname match cl-lib macros?, Eli Zaretskii, 2019/03/16
- Re: Should diff.elisp.xfuncname match cl-lib macros?, Andreas Schwab, 2019/03/17
- Re: Should diff.elisp.xfuncname match cl-lib macros?, Basil L. Contovounesios, 2019/03/17
- Re: Should diff.elisp.xfuncname match cl-lib macros?, Juri Linkov, 2019/03/17
- Re: Should diff.elisp.xfuncname match cl-lib macros?, Stefan Monnier, 2019/03/17
- Re: Should diff.elisp.xfuncname match cl-lib macros?, Juri Linkov, 2019/03/18