unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gunnar Horrigmo <horrigmo@runbox.no>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: Thomas Fitzsimmons <fitzsim@fitzsim.org>, 46056@debbugs.gnu.org
Subject: bug#46056: hardcoded ~/.emacs.d in elpa package excorporate
Date: Sun, 24 Jan 2021 03:45:17 +0100	[thread overview]
Message-ID: <iv4eeibjbnm.fsf@hot-rats.uio.no> (raw)
In-Reply-To: <878s8jz3ny.fsf@tcd.ie> (Basil L. Contovounesios's message of "Sat, 23 Jan 2021 22:31:13 +0000")

"Basil L. Contovounesios" <contovob@tcd.ie> writes:

> Right.  CCing Thomas, the package's maintainer.

Thank you.


> Rather than concatenating file names as strings, better to use
> locate-user-emacs-file in this case (or expand-file-name in general).
> See (info "(elisp) Standard File Names").

Good advice! 


> Ideally the patch would include a ChangeLog-style commit message
> referencing this bug number; see the guidelines in the CONTRIBUTE
> file[1] at the top of the Emacs source tree.  Otherwise looks fine :).
>
> [1]: https://git.savannah.gnu.org/cgit/emacs.git/tree/CONTRIBUTE

Not that Thomas needs my help, but just for my own excercise, is this
what you prefer?

Subject: [PATCH] Use `locate-user-emacs-file' instead of hardcoded paths to
 diary files

---
 excorporate-diary.el | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/excorporate-diary.el b/excorporate-diary.el
index 833df3017c..d936f6494c 100644
--- a/excorporate-diary.el
+++ b/excorporate-diary.el
@@ -76,13 +76,13 @@ respectively."
              #'exco-diary-icalendar--add-diary-entry-around))
 
 (defvar excorporate-diary-today-file
-  "~/.emacs.d/excorporate/diary-excorporate-today"
+  (locate-user-emacs-file "excorporate/diary-excorporate-today")
   "The diary file where Excorporate should save today's meetings.
 This file will be #include'd in `diary-file' by
 `excorporate-diary-enable'.")
 
 (defvar excorporate-diary-transient-file
-  "~/.emacs.d/excorporate/diary-excorporate-transient"
+  (locate-user-emacs-file "excorporate/diary-excorporate-transient")
   "The diary file where Excorporate should save retrieved meetings.
 This file will be #include'd in `diary-file' by
 `excorporate-diary-enable'.")
-- 
2.30.0

-- 
Gunnar





  reply	other threads:[~2021-01-24  2:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-23 18:13 bug#46056: hardcoded ~/.emacs.d in elpa package excorporate Gunnar Horrigmo
2021-01-23 22:31 ` Basil L. Contovounesios
2021-01-24  2:45   ` Gunnar Horrigmo [this message]
2021-01-24  3:16     ` Thomas Fitzsimmons
2021-01-24  9:21       ` Michael Albinus
2021-01-24 17:34         ` Thomas Fitzsimmons
2021-01-24 17:40           ` Michael Albinus
2021-01-24 12:04       ` Basil L. Contovounesios
2021-01-24 12:48       ` Gunnar Horrigmo
2021-01-24 11:58     ` Basil L. Contovounesios

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=iv4eeibjbnm.fsf@hot-rats.uio.no \
    --to=horrigmo@runbox.no \
    --cc=46056@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=fitzsim@fitzsim.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).