unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lele Gaifax <lele@metapensiero.it>
To: emacs-devel@gnu.org
Subject: Strange problem with emacs-lisp/copyright.el
Date: Tue, 11 Apr 2017 08:53:21 +0200	[thread overview]
Message-ID: <87o9w3ph9a.fsf@nautilus> (raw)

Hi all,

since a couple of week I switched my main development environment to Emacs
master, and I'm quite happy.

The only problem I had is one strange defect I'm hitting that, despite all my
efforts to reproduce it, I'm still unable to understand the nature. It seems
very similar to bug#2209, now archived.

In my setup I've configured

  (add-hook 'before-save-hook #'copyright-update)

to automatically update the copyright years range in files header. Accordingly
to the VC tool, I installed that setup more than one year ago and never
noticed any problem, with Emacs 25.

With the new Emacs, when I save multiple files that wasn't yet touched in the
current year, *sometime* and *some files* the new year is added in the wrong
location, that is the new year (that is, the string ", 2017") gets added
somewhere in the file, not where it should go: most of the times at the
beginning of a line, sometime in the middle, in any case apparently at the
`point' location, where the cursor was at save time.

As said, I've tried several times to understand what's going on, either with
edebug-ing the `copyright-update-year' function or decorating it with a few
`message' calls to emit the updated location and such, but it seems some sort
of eisenbug... I even reverted my source tree to the exact state before this
happened, and applied the very same set of mechanical replacements (I was
fixing a single typo and I used wgrep to spot and correct all instances), with
no luck.

Do this ring any bell, or can some one hints me on a better/more effective way
to investigate the issue, before opening a new bug report?

Thanks in advance,
ciao, lele.
-- 
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
lele@metapensiero.it  |                 -- Fortunato Depero, 1929.




             reply	other threads:[~2017-04-11  6:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11  6:53 Lele Gaifax [this message]
2017-04-11  9:28 ` Strange problem with emacs-lisp/copyright.el Alan Third
2017-04-17 17:29 ` Lele Gaifax
2017-04-21 17:49   ` Lele Gaifax
2017-04-22 13:21     ` Johan Bockgård
2017-04-23 21:00       ` Lele Gaifax
2017-05-05  9:36         ` Lele Gaifax
2017-10-31 18:14           ` Lele Gaifax
2017-11-01  2:19             ` Noam Postavsky
2017-11-05 11:36             ` Johan Bockgård

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=87o9w3ph9a.fsf@nautilus \
    --to=lele@metapensiero.it \
    --cc=emacs-devel@gnu.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).