From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Should diff.elisp.xfuncname match cl-lib macros?
Date: Sun, 17 Mar 2019 05:37:41 +0200 [thread overview]
Message-ID: <838sxexjay.fsf@gnu.org> (raw)
In-Reply-To: <87ftrmeb80.fsf@tcd.ie> (contovob@tcd.ie)
> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Cc: <monnier@iro.umontreal.ca>, <emacs-devel@gnu.org>
> Date: Sat, 16 Mar 2019 21:54:55 +0000
>
> > So I think until we fix this basic deficiency, extending that to more
> > symbols will just add to the mess. YMMV.
>
> Which deficiency do you mean? That 'git log -L' picks up
> next-line-or-history-element instead of next-line in your example,
> i.e. that it's currently inaccurate?
Yes.
> How do you usually use this feature?
With commands such as the one I show above. It's supposed to show the
history of changes in the named function, but instead it almost always
shows unrelated history.
next prev parent reply other threads:[~2019-03-17 3:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 16:42 Should diff.elisp.xfuncname match cl-lib macros? Basil L. Contovounesios
2019-03-15 18:21 ` Stefan Monnier
2019-03-16 3:56 ` Richard Stallman
2019-03-16 15:33 ` cl-defun vs defun (was: Should diff.elisp.xfuncname match cl-lib macros?) Basil L. Contovounesios
2019-03-17 2:41 ` Richard Stallman
2019-03-16 15:30 ` Should diff.elisp.xfuncname match cl-lib macros? Basil L. Contovounesios
2019-03-16 16:42 ` Eli Zaretskii
2019-03-16 17:12 ` Stefan Monnier
2019-03-16 17:33 ` Eli Zaretskii
2019-03-16 18:14 ` Stefan Monnier
2019-03-16 21:55 ` Basil L. Contovounesios
2019-03-16 21:54 ` Basil L. Contovounesios
2019-03-17 3:37 ` Eli Zaretskii [this message]
2019-03-17 8:14 ` Andreas Schwab
2019-03-17 15:22 ` Basil L. Contovounesios
2019-03-17 21:33 ` Juri Linkov
2019-03-18 1:14 ` Stefan Monnier
2019-03-18 21:02 ` Juri Linkov
2019-05-13 1:40 ` Basil L. Contovounesios
2019-05-20 15:03 ` Basil L. Contovounesios
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838sxexjay.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).