From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: 900276502f..: Paul Eggert 2018-11-13 Act like POSIX sh if $HOME is relative
Date: Wed, 12 Dec 2018 17:55:12 +0100 [thread overview]
Message-ID: <8736r2r8gf.fsf@telefonica.net> (raw)
In-Reply-To: CALDnm53ECggeo=S30xdJbOCRDum98KiqpNnd5Kbet-r0bne2fQ@mail.gmail.com
João Távora <joaotavora@gmail.com> writes:
> On Wed, Dec 12, 2018 at 3:15 PM Óscar Fuentes <ofv@wanadoo.es> wrote:
>
>>
>>
>> You are asking for being bug-compatible with previous Emacs because you
>> must cope with bugs on other applications :-)
>
>
> Yes, if you will. That is what the world is like.
Yes, sadly :-)
>> Do you think that this
>> problem is frequent enough?
>
>
> Every time I start Emacs, or everytime someone in my $DAYJOB starts Emacs
> after upgrading to Emacs 27. Frequent enough?
I was asking about an heuristic to estimate the hypothetical fraction of
affected users. Something like "I know two guys on the Internet with the
same problem."
>> What applications are those that don't admit
>> an slash after the volume letter in HOME?
>>
>
> 30-year+ old, big bad misbehaving Lisp-based applications. Kinda like
> Emacs, I suppose :-)
Let me guess: those applications share the same runtime and/or
libraries.
FWIW, I'm not opposed to keeping Emacs bug-compatible on this case. (As
if my opinion had some value :-)
next prev parent reply other threads:[~2018-12-12 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 12:42 900276502f..: Paul Eggert 2018-11-13 Act like POSIX sh if $HOME is relative João Távora
2018-12-12 13:19 ` Yuri Khan
2018-12-12 14:54 ` João Távora
2018-12-12 15:22 ` Eli Zaretskii
2018-12-12 15:29 ` Drew Adams
2018-12-12 16:35 ` Eli Zaretskii
2018-12-12 13:28 ` Óscar Fuentes
2018-12-12 14:53 ` João Távora
2018-12-12 15:14 ` Óscar Fuentes
2018-12-12 15:28 ` João Távora
2018-12-12 16:55 ` Óscar Fuentes [this message]
2018-12-12 17:19 ` João Távora
2018-12-12 17:20 ` Eli Zaretskii
2018-12-12 15:16 ` Stefan Monnier
2018-12-12 16:30 ` Eli Zaretskii
2018-12-12 15:20 ` Eli Zaretskii
2018-12-12 15:30 ` João Távora
2018-12-12 16:35 ` 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=8736r2r8gf.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=emacs-devel@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.