all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yilkal Argaw <yilkalargawworkneh@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: missing "/" in value of user-emacs-directory when using --init-directory flag
Date: Tue, 29 Nov 2022 20:20:10 +0200	[thread overview]
Message-ID: <83sfi1lj1h.fsf@gnu.org> (raw)
In-Reply-To: <CAJddU=rTA9YxXJA98b0Yp5bBkLCFH=r1jxOqXngQ9JX3tccimQ@mail.gmail.com> (message from Yilkal Argaw on Tue, 29 Nov 2022 17:55:45 +0000)

> From: Yilkal Argaw <yilkalargawworkneh@gmail.com>
> Date: Tue, 29 Nov 2022 17:55:45 +0000
> 
> In my configs I use (concat user-emacs-directory "somedirectory or
> file") to refer to files with respect to emacs. When loading emacs
> with the option --init-directory this
> this string is not separated by a backslash since the value
> user-emacs-directory does not have a backslash on the end of it. This
> might break previous configs so it should be standardized to contain
> the same string value in both cases.

Don't use 'concat' for file names; use expand-file-name instead.



  parent reply	other threads:[~2022-11-29 18:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 17:55 missing "/" in value of user-emacs-directory when using --init-directory flag Yilkal Argaw
2022-11-29 18:11 ` Yilkal Argaw
2022-11-29 18:20 ` Eli Zaretskii [this message]
2022-11-29 18:56   ` [External] : " Drew Adams
2022-11-29 19:01     ` Greg Farough
2022-11-29 20:08       ` Stefan Monnier
2022-11-29 20:58         ` Greg Farough
2022-11-29 21:54         ` Juanma Barranquero
2022-11-29 23:04           ` Drew Adams
2022-11-29 23:02         ` Drew Adams
2022-12-02 22:47           ` Richard Stallman
2022-12-03  6:47             ` Yuri Khan
2022-12-02 13:20   ` Robin Tarsiger
2022-12-12  3:41     ` Yilkal Argaw
2022-12-12 12:23       ` Eli Zaretskii
2022-12-12 18:04         ` Yilkal Argaw
2022-12-12 18:13           ` Eli Zaretskii

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=83sfi1lj1h.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yilkalargawworkneh@gmail.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.