unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: rms@gnu.org
Cc: Drew Adams <drew.adams@oracle.com>,
	monnier@iro.umontreal.ca, gregf@gnu.org, emacs-devel@gnu.org
Subject: Re: [External] : Re: missing "/" in value of user-emacs-directory when using --init-directory flag
Date: Sat, 3 Dec 2022 13:47:26 +0700	[thread overview]
Message-ID: <CAP_d_8V3-Dn9xG1eWgg_jhkjtLtRtJWFOc+0TPqTdQ0Ns=iS=Q@mail.gmail.com> (raw)
In-Reply-To: <E1p1Eos-0001Ds-GZ@fencepost.gnu.org>

On Sat, 3 Dec 2022 at 05:49, Richard Stallman <rms@gnu.org> wrote:

>   > > Maybe we could tweak the byte-compiler so it emits congratulatory
>   > > messages for every 10-or-so uses of `expand-file-name`?
>
>   > That's if option `reinforcement' is contains
>   > symbol `positive'.  If the list value contains
>   > `negative' then it can emit warnings to impose
>   > appropriate penalties (TBD).  If both then both.
>
> How about a flag to make `concat' detect that you're doing
> file name concatenation and enter the debugger?

You’re dangerously close to inventing a type system ;)



  reply	other threads:[~2022-12-03  6:47 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
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 [this message]
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

  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='CAP_d_8V3-Dn9xG1eWgg_jhkjtLtRtJWFOc+0TPqTdQ0Ns=iS=Q@mail.gmail.com' \
    --to=yuri.v.khan@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=gregf@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@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 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).