From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: feature proposal? add-change-log-entry does not find the ChangeLog file: change-log-directory-files
Date: Wed, 05 Sep 2018 10:01:19 +0200 [thread overview]
Message-ID: <87zhwwqsog.fsf@mat.ucm.es> (raw)
In-Reply-To: 874lf541ss.fsf@red-bean.com
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
> Uwe Brauer <oub@mat.ucm.es> writes:
> A moment ago, I followed up with a proposal to walk up the tree --
> which turns out to be what the current behavior is supposed to be
> anyway, and is what you expected -- because I didn't realize that that
> behavior was already implemented.
> Then I read the doc string for `find-change-log' and the behavior
> described there seems to be exactly what you wanted and expected.
This is my understanding too, reading the documentation. However in my case
emacs *does* not walk up the tree, it offers me to open a (non existing)
ChangeLog file in the current directory, which I found annoying.
> So I *think* the behavior you want is the behavior Emacs is already
> supposed to have. Have you simply discovered a bug, or is there
> something subtle about your situation that is not covered by the
> current intended behavior of `find-change-log'?
I think I have to debug it, starting with emacs -q.
Thanks
Uwe
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2018-09-05 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 10:34 feature proposal? add-change-log-entry does not find the ChangeLog file: change-log-directory-files Uwe Brauer
2018-09-04 17:11 ` Karl Fogel
2018-09-04 17:20 ` Karl Fogel
2018-09-05 8:01 ` Uwe Brauer [this message]
2018-09-05 11:07 ` Uwe Brauer
2018-09-05 13:32 ` [SOLVED] (was: feature proposal? add-change-log-entry does not find the ChangeLog file: change-log-directory-files) Uwe Brauer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhwwqsog.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.