From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Masatake YAMATO <yamato@redhat.com>
Cc: 28685@debbugs.gnu.org
Subject: bug#28685: 25.3; wrong handling ~/.cpp.el
Date: Sat, 14 Oct 2017 01:38:47 -0400 [thread overview]
Message-ID: <87mv4u9tlk.fsf@users.sourceforge.net> (raw)
In-Reply-To: <20171003.201905.799741493914957289.yamato@redhat.com> (Masatake YAMATO's message of "Tue, 03 Oct 2017 20:19:05 +0900 (JST)")
tags 28685 + patch
quit
Masatake YAMATO <yamato@redhat.com> writes:
> cpp.el tries to load ./.cpp.el even when it is not readable. Though
> it checks ~/.cpp.el can be readable, it still tries to load ./.cpp.el.
Thanks, the patch looks good. But since this bug has apparently been
present since the initial revision in 1994 and nobody ever noticed until
now, I wonder if we should instead just remove the ~/.cpp.el feature
altogether.
next prev parent reply other threads:[~2017-10-14 5:38 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 [this message]
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
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=87mv4u9tlk.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=28685@debbugs.gnu.org \
--cc=yamato@redhat.com \
/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.