From: Masatake YAMATO <yamato@redhat.com>
To: rgm@gnu.org
Cc: 28685@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#28685: 25.3; wrong handling ~/.cpp.el
Date: Tue, 17 Oct 2017 19:23:03 +0900 (JST) [thread overview]
Message-ID: <20171017.192303.945206897976012626.yamato@redhat.com> (raw)
In-Reply-To: <mk8tgdpeh1.fsf@fencepost.gnu.org>
On Sat, 14 Oct 2017 18:11:06 -0400, Glenn Morris <rgm@gnu.org> wrote:
> Eli Zaretskii wrote:
>
>>> E.g. this entry from NEWS.24:
>>>
>>> ** More packages look for ~/.emacs.d/<foo> additionally to ~/.<foo>.
>>
>> I'm okay with looking in both places.
>
> This is what locate-user-emacs-file is for.
How about following extra patch?
Ideally, ~/.emacs.d/.cpp.el should be ~/.emacs.d/cpp.el.
However, I cannot find good way to implement it.
commit 765dfed4bd1ea1a3b6d9b51383fa0ec745479cce (HEAD -> cpp-highlight-check)
Author: Masatake YAMATO <yamato@redhat.com>
Date: Tue Oct 17 19:20:38 2017 +0900
Put .cpp.el to ~/.emacs.d if possible
*lisp/progmodes/cpp.el (cpp-edit-load): Use locate-user-emacs-file
instead of specifying "~/"
(cpp-edit-save): Ditto.
diff --git a/lisp/progmodes/cpp.el b/lisp/progmodes/cpp.el
index 3a7dab72b4..0a68a0cf2c 100644
--- a/lisp/progmodes/cpp.el
+++ b/lisp/progmodes/cpp.el
@@ -576,8 +576,8 @@ cpp-edit-load
nil)
((file-readable-p cpp-config-file)
(load-file cpp-config-file))
- ((file-readable-p (concat "~/" cpp-config-file))
- (load-file (concat "~/" cpp-config-file))))
+ ((file-readable-p (locate-user-emacs-file cpp-config-file))
+ (load-file (locate-user-emacs-file cpp-config-file))))
(if (derived-mode-p 'cpp-edit-mode)
(cpp-edit-reset)))
@@ -588,7 +588,7 @@ cpp-edit-save
(with-current-buffer cpp-edit-buffer
(let* ((config-file (if (file-writable-p cpp-config-file)
cpp-config-file
- (concat "~/" cpp-config-file)))
+ (locate-user-emacs-file cpp-config-file)))
(buffer (find-file-noselect config-file))
)
(set-buffer buffer)
next prev parent reply other threads:[~2017-10-17 10:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 11:19 bug#28685: 25.3; wrong handling ~/.cpp.el Masatake YAMATO
2017-10-14 5:38 ` Noam Postavsky
2017-10-14 7:21 ` Eli Zaretskii
2017-10-14 14:14 ` Noam Postavsky
2017-10-14 15:01 ` Eli Zaretskii
2017-10-14 15:17 ` Noam Postavsky
2017-10-14 15:32 ` Eli Zaretskii
2017-10-14 22:11 ` Glenn Morris
2017-10-17 10:23 ` Masatake YAMATO [this message]
2017-10-17 12:43 ` Noam Postavsky
2017-10-17 14:53 ` Eli Zaretskii
2017-10-19 18:55 ` Masatake YAMATO
2017-10-19 19:12 ` Masatake YAMATO
2017-10-21 0:44 ` Noam Postavsky
2017-10-21 7:14 ` Eli Zaretskii
2017-10-21 20:16 ` Noam Postavsky
2017-10-22 9:22 ` bug#28685: [PATCH 1/3] Fix reading and writing cpp-config-file under home directory Masatake YAMATO
2017-10-22 9:22 ` bug#28685: [PATCH 2/3] Put .cpp.el to ~/.emacs.d if possible Masatake YAMATO
2017-10-22 9:22 ` bug#28685: [PATCH 3/3] Put cpp config file to ~/.emacs.d/cpp.el " Masatake YAMATO
2017-10-22 16:41 ` Noam Postavsky
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=20171017.192303.945206897976012626.yamato@redhat.com \
--to=yamato@redhat.com \
--cc=28685@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
--cc=rgm@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.