From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 37395@debbugs.gnu.org
Subject: bug#37395: [PATCH v4] diff-mode.el: take into account patch separators
Date: Wed, 09 Oct 2019 23:08:16 +0300 [thread overview]
Message-ID: <1570651696.135652.4@yandex.ru> (raw)
In-Reply-To: <87mue9678m.fsf@gnus.org>
Ah, sorry, I missed it. v5 sent, now should be no new warnings.
On Ср, окт 9, 2019 at 21:36, Lars Ingebrigtsen <larsi@gnus.org>
wrote:
> Konstantin Kharlamov <Hi-Angel@yandex.ru> writes:
>
>> * lisp/vc/diff-mode.el (diff-prev-line-if-patch-separator):
>> A function to return prev. line if it has git-format-patch
>> separator.
>> (diff-end-of-hunk): Make use of
>> diff-prev-line-if-patch-separator
>> diff-buffer-type: whether a buffer is a git-diff
>> (define-derived-mode): set diff-buffer-type to appropriate
>> value
>
> Byte-compiling gives:
>
> In diff-prev-line-if-patch-separator:
> vc/diff-mode.el:516:10:Warning: reference to free variable
> `diff-buffer-type'
> vc/diff-mode.el:517:7:Warning: `previous-line' is for interactive use
> only;
> use `forward-line' with negative argument instead.
>
> So you have to move the defvar earlier and adjust the previous-line,
> but
> otherwise I think it looks OK...
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-09 20:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 21:33 bug#37395: Diff-mode doesn't take into account patch-separators as produced by git-format-patch Konstantin Kharlamov
2019-09-12 21:34 ` bug#37395: [PATCH] diff-mode.el: take into account patch separators Konstantin Kharlamov
2019-09-13 6:14 ` Eli Zaretskii
2019-09-13 6:58 ` Konstantin Kharlamov
2019-09-16 20:31 ` Konstantin Kharlamov
2019-09-13 9:19 ` bug#37395: [PATCH v2] " Konstantin Kharlamov
2019-09-16 20:26 ` bug#37395: [PATCH v3] " Konstantin Kharlamov
2019-10-07 4:39 ` Lars Ingebrigtsen
2019-10-07 23:04 ` Konstantin Kharlamov
2019-10-07 23:12 ` Konstantin Kharlamov
2019-10-08 15:59 ` Lars Ingebrigtsen
2019-10-08 20:08 ` Konstantin Kharlamov
2019-10-08 19:34 ` bug#37395: [PATCH v4] " Konstantin Kharlamov
2019-10-09 19:36 ` Lars Ingebrigtsen
2019-10-09 20:08 ` Konstantin Kharlamov [this message]
2019-10-09 20:07 ` bug#37395: [PATCH v5] " Konstantin Kharlamov
2019-10-13 3:53 ` Lars Ingebrigtsen
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=1570651696.135652.4@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=37395@debbugs.gnu.org \
--cc=larsi@gnus.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.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).