unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel <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 15:28:49 +0000	[thread overview]
Message-ID: <CALDnm53ECggeo=S30xdJbOCRDum98KiqpNnd5Kbet-r0bne2fQ@mail.gmail.com> (raw)
In-Reply-To: <877egerd4e.fsf@telefonica.net>

[-- Attachment #1: Type: text/plain, Size: 657 bytes --]

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.



> 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?



> 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 :-)

João

[-- Attachment #2: Type: text/html, Size: 1250 bytes --]

  reply	other threads:[~2018-12-12 15:28 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 [this message]
2018-12-12 16:55         ` Óscar Fuentes
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

  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='CALDnm53ECggeo=S30xdJbOCRDum98KiqpNnd5Kbet-r0bne2fQ@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    /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).