emacs: could not resolve realpath of "(null)": No such file or directory [master]

emacs: could not resolve realpath of "(null)": No such file or directory [master]

[Kaushal Modi]

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

Hello,

Some commit over this past weekend severely broke emacs for me.

I am on RHEL 6.8. It builds fine, but when I do emacs &, I get this error:

> emacs: could not resolve realpath of "(null)": No such file or directory

If nobody else is seeing this issue, I can debug this further on my end. My
last working Emacs was from this Friday commit
869cf5cbc0721bbe9e4df557f4ed3633fb13c05f.

--
Kaushal Modi

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

Re: emacs: could not resolve realpath of "(null)": No such file or directory [master]

[Kaushal Modi]

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

On Mon, Jun 24, 2019 at 9:39 AM Kaushal Modi <kaushal.modi@gmail.com> wrote:

> Hello,
>
> Some commit over this past weekend severely broke emacs for me.
>
> I am on RHEL 6.8. It builds fine, but when I do emacs &, I get this error:
>
> > emacs: could not resolve realpath of "(null)": No such file or directory
>

To add, emacs -Q also gives the same error.

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

Re: emacs: could not resolve realpath of "(null)": No such file or directory [master]

[Óscar Fuentes]

Kaushal Modi <kaushal.modi@gmail.com> writes:

>> Some commit over this past weekend severely broke emacs for me.
>>
>> I am on RHEL 6.8. It builds fine, but when I do emacs &, I get this error:
>>
>> > emacs: could not resolve realpath of "(null)": No such file or directory
>>
>
> To add, emacs -Q also gives the same error.

The 3 threads previous to yours are about this problem :-)

Daniel just pushed a fix and it works for me (TM).

Re: emacs: could not resolve realpath of "(null)": No such file or directory [master]

[Kaushal Modi]

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

On Mon, Jun 24, 2019 at 9:59 AM Óscar Fuentes <ofv@wanadoo.es> wrote:

>
> The 3 threads previous to yours are about this problem :-)
>

Oops.

Daniel just pushed a fix and it works for me (TM).
>

Yes, I confirm the fix on my end too (I call emacsclient via an alias named
"e" and that's working fine too).

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