Modified remote file name syntax

Modified remote file name syntax

[Michael Albinus]

Hi,

today I've committed a patch, which changes the remote file name syntax
in Emacs. The "method" part, optional until now, becomes
mandatory. Valid remote file names are now

/method:host:/path/to/file
/method:user@host:/path/to/file

A new method, "-", has been added which is a marker for the default
method as known so far.

The reason is, that all the time there have been problems in Tramp due
to syntactic ambiguities. A remote file name "/foo:" has not been
distinct; "foo" could be either a method or a host name. This has
resulted in permanent problems during file name completion.

The changes will be visible with the next releases of Tramp 2.3.2 and
Emacs 26.1.

Best regards, Michael.

Re: Modified remote file name syntax

[Nick Dokos]

Heads-up: if you are using remote directories, you'll want to read this.

Michael Albinus <michael.albinus@gmx.de> writes:

> Hi,
>
> today I've committed a patch, which changes the remote file name syntax
> in Emacs. The "method" part, optional until now, becomes
> mandatory. Valid remote file names are now
>
> /method:host:/path/to/file
> /method:user@host:/path/to/file
>
> A new method, "-", has been added which is a marker for the default
> method as known so far.
>
> The reason is, that all the time there have been problems in Tramp due
> to syntactic ambiguities. A remote file name "/foo:" has not been
> distinct; "foo" could be either a method or a host name. This has
> resulted in permanent problems during file name completion.
>
> The changes will be visible with the next releases of Tramp 2.3.2 and
> Emacs 26.1.
>
> Best regards, Michael.

-- 
Nick

Re: Modified remote file name syntax

[Tino Calancha]

On Mon, 13 Mar 2017, Michael Albinus wrote:

> Hi,
>
> today I've committed a patch, which changes the remote file name syntax
> in Emacs. The "method" part, optional until now, becomes
> mandatory. Valid remote file names are now
>
> /method:host:/path/to/file
> /method:user@host:/path/to/file
>
> A new method, "-", has been added which is a marker for the default
> method as known so far.
>
> The reason is, that all the time there have been problems in Tramp due
> to syntactic ambiguities. A remote file name "/foo:" has not been
> distinct; "foo" could be either a method or a host name. This has
> resulted in permanent problems during file name completion.

Hi Michael,

after your commit ed33337c3e0d0b1a8b140e23168421ea43d79324
i cannot launch emacs with a symbolic link.

To reproduce:

;; Make a link to the emacs executable in a dir inside your PATH.
;; For instance, i have the link ~/bin/emacs
(if (member (file-name-as-directory (expand-file-name "~/bin")) 
(parse-colon-path (getenv "PATH")))
     (message "OK, '~/bin' is in PATH")
   (error "'~/bin' not in PATH"))

;; Launch Emacs using this link.
M-& emacs -Q ; It doesn't work.

;; Note that the following is OK:
M-& ~/soft/emacs-master/src/emacs -Q

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
In GNU Emacs 26.0.50 (build 6, x86_64-pc-linux-gnu, GTK+ Version 3.22.8)
  of 2017-03-14 built on calancha-pc
Repository revision: ed33337c3e0d0b1a8b140e23168421ea43d79324
Windowing system distributor 'The X.Org Foundation', version 11.0.11902000
System Description:	Debian GNU/Linux 9.0 (stretch)

Re: Modified remote file name syntax

[Michael Albinus]

Tino Calancha <tino.calancha@gmail.com> writes:

> Hi Michael,

Hi Tino,

> after your commit ed33337c3e0d0b1a8b140e23168421ea43d79324
> i cannot launch emacs with a symbolic link.
>
> To reproduce:
>
> ;; Make a link to the emacs executable in a dir inside your PATH.
> ;; For instance, i have the link ~/bin/emacs
> (if (member (file-name-as-directory (expand-file-name "~/bin"))
> (parse-colon-path (getenv "PATH")))
>     (message "OK, '~/bin' is in PATH")
>   (error "'~/bin' not in PATH"))
>
> ;; Launch Emacs using this link.
> M-& emacs -Q ; It doesn't work.

I've followed your recipe exactly. The emacs is the recent one:

--8<---------------cut here---------------start------------->8---
C-h C-a
GNU Emacs 26.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.20.9)
 of 2017-03-14

M-& which emacs
/home/albinmic/bin/emacs

M-& ls -l `which emacs`
lrwxrwxrwx 1 albinmic albinmic 34 Mär 14 09:36 /home/albinmic/bin/emacs -> /home/albinmic/src/emacs/src/emacs

M-& ls -l /home/albinmic/src/emacs/src/emacs
-rwxrwxr-x 3 albinmic albinmic 56720584 Mär 14 08:43 /home/albinmic/src/emacs/src/emacs

M-& emacs -Q
--8<---------------cut here---------------end--------------->8---

It comes up. So I don't know why it doesn't work for you :-(

Best regards, Micahel.

Re: Modified remote file name syntax

[Tino Calancha]

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



On Tue, 14 Mar 2017, Michael Albinus wrote:

> I've followed your recipe exactly. The emacs is the recent one:
>
> --8<---------------cut here---------------start------------->8---
> C-h C-a
> GNU Emacs 26.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.20.9)
> of 2017-03-14
>
> M-& which emacs
> /home/albinmic/bin/emacs
>
> M-& ls -l `which emacs`
> lrwxrwxrwx 1 albinmic albinmic 34 Mär 14 09:36 /home/albinmic/bin/emacs -> /home/albinmic/src/emacs/src/emacs
>
> M-& ls -l /home/albinmic/src/emacs/src/emacs
> -rwxrwxr-x 3 albinmic albinmic 56720584 Mär 14 08:43 /home/albinmic/src/emacs/src/emacs
>
> M-& emacs -Q
> --8<---------------cut here---------------end--------------->8---
>
> It comes up. So I don't know why it doesn't work for you :-(
It might be because i don't use a stable release of Debian.  I update
it mostly every day.

Thank you.  Your receipt looks identical:

M-& which emacs
/home/calancha/bin/emacs

M-& ls -l `which emacs`
lrwxrwxrwx 1 calancha calancha 42 Mar 14 11:11 /home/calancha/bin/emacs -> /home/calancha/soft/emacs-master/src/emacs
M-& emacs -Q

I see following error in *Async Shell Command*:
(maybe someone suspect something)

Warning: arch-dependent data dir '/usr/local/libexec/emacs/26.0.50/x86_64-pc-linux-gnu/': No such file or directory
Warning: Lisp directory '/usr/local/share/emacs/26.0.50/lisp': No such file or directory
Warning: Could not find simple.el or simple.elc
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "pk-gtk-module"

The new Emacs instance shows the *scratch* buffer and the error:
Cannot open load file: No such file or directory, mule-util

Following also works fine.
M-& which ~/bin/emacs -Q

If i checkout the commit right before yours, that is
f591765e2b6b9ec3fa3ff647c77a10c984f78133
i don't reproduce the issue.

Re: Modified remote file name syntax

[Michael Albinus]

Tino Calancha <tino.calancha@gmail.com> writes:

> I see following error in *Async Shell Command*:
> (maybe someone suspect something)
>
> Warning: arch-dependent data dir
> '/usr/local/libexec/emacs/26.0.50/x86_64-pc-linux-gnu/': No such file
> or directory
> Warning: Lisp directory '/usr/local/share/emacs/26.0.50/lisp': No such
> file or directory
> Warning: Could not find simple.el or simple.elc
> Gtk-Message: Failed to load module "pk-gtk-module"
> Gtk-Message: Failed to load module "pk-gtk-module"
>
> The new Emacs instance shows the *scratch* buffer and the error:
> Cannot open load file: No such file or directory, mule-util
>
> Following also works fine.
> M-& which ~/bin/emacs -Q
>
> If i checkout the commit right before yours, that is
> f591765e2b6b9ec3fa3ff647c77a10c984f78133
> i don't reproduce the issue.

Did you run "make bootstrap"? My commit changes autoloads; while working
on the patch I was urged several time to run a bootstrap in order to
bring Emacs in a proper state.

Best regards, Michael.

Re: Modified remote file name syntax

[Tino Calancha]

On Tue, 14 Mar 2017, Michael Albinus wrote:

> Tino Calancha <tino.calancha@gmail.com> writes:
>
>> I see following error in *Async Shell Command*:
>> (maybe someone suspect something)
>>
>> Warning: arch-dependent data dir
>> '/usr/local/libexec/emacs/26.0.50/x86_64-pc-linux-gnu/': No such file
>> or directory
>> Warning: Lisp directory '/usr/local/share/emacs/26.0.50/lisp': No such
>> file or directory
>> Warning: Could not find simple.el or simple.elc
>> Gtk-Message: Failed to load module "pk-gtk-module"
>> Gtk-Message: Failed to load module "pk-gtk-module"
>>
>> The new Emacs instance shows the *scratch* buffer and the error:
>> Cannot open load file: No such file or directory, mule-util
>>
>> Following also works fine.
>> M-& which ~/bin/emacs -Q
>>
>> If i checkout the commit right before yours, that is
>> f591765e2b6b9ec3fa3ff647c77a10c984f78133
>> i don't reproduce the issue.
>
> Did you run "make bootstrap"? My commit changes autoloads; while working
> on the patch I was urged several time to run a bootstrap in order to
> bring Emacs in a proper state.
Yes i did.  The problem still arise.

Re: Modified remote file name syntax

[Michael Albinus]

Tino Calancha <tino.calancha@gmail.com> writes:

Hi Tino,

> On Tue, 14 Mar 2017, Michael Albinus wrote:
>
>> Tino Calancha <tino.calancha@gmail.com> writes:
>>
>>> I see following error in *Async Shell Command*:
>>> (maybe someone suspect something)
>>>
>>> Warning: arch-dependent data dir
>>> '/usr/local/libexec/emacs/26.0.50/x86_64-pc-linux-gnu/': No such file
>>> or directory
>>> Warning: Lisp directory '/usr/local/share/emacs/26.0.50/lisp': No such
>>> file or directory
>>> Warning: Could not find simple.el or simple.elc
>>> Gtk-Message: Failed to load module "pk-gtk-module"
>>> Gtk-Message: Failed to load module "pk-gtk-module"
>>>
>>> The new Emacs instance shows the *scratch* buffer and the error:
>>> Cannot open load file: No such file or directory, mule-util
>>>
>>> Following also works fine.
>>> M-& which ~/bin/emacs -Q
>>>
>>> If i checkout the commit right before yours, that is
>>> f591765e2b6b9ec3fa3ff647c77a10c984f78133
>>> i don't reproduce the issue.
>>
>> Did you run "make bootstrap"? My commit changes autoloads; while working
>> on the patch I was urged several time to run a bootstrap in order to
>> bring Emacs in a proper state.
> Yes i did.  The problem still arise.

I have no further idea. However, messages like "Warning: Lisp directory
'/usr/local/share/emacs/26.0.50/lisp': No such file or directory" look
very suspicious.

If you run this constellation prior my patch (everything works fine),
could you check in the running Emacs where simple.el and other files are
located according to M-x locate-library ?

It seems also to me, that /usr/local/share/emacs/26.0.50/lisp should not
be in game. I suppose, that you haven't run "make install" yet;
everything at /usr/local/share might not contain the recent changes.

Best regards, Michael.

Re: Modified remote file name syntax

[Tino Calancha]

On Tue, 14 Mar 2017, Michael Albinus wrote:

> I have no further idea. However, messages like "Warning: Lisp directory
> '/usr/local/share/emacs/26.0.50/lisp': No such file or directory" look
> very suspicious.
>
> If you run this constellation prior my patch (everything works fine),
> could you check in the running Emacs where simple.el and other files are
> located according to M-x locate-library ?
I have one instance of Emacs started with -Q
(version: f591765e2b6b9ec3fa3ff647c77a10c984f78133)

M-x locate-library RET simple RET
Library is file ~/soft/emacs-master/lisp/simple.elc

> It seems also to me, that /usr/local/share/emacs/26.0.50/lisp should not
> be in game. I suppose, that you haven't run "make install" yet;
That's right, i didn't run "make install".  Everything is under:
~/soft/emacs-master

$> ls -l /usr/local/share/emacs/
total 12
drwxrwsr-x 3 root staff 4096 Feb  2 17:09 24.5
drwxrwsr-x 3 root staff 4096 Feb 26 13:48 25.1
drwxrwsr-x 2 root staff 4096 May 30  2016 site-lisp
;; There is no 26.1 as expected.

M-: (dired "~/soft/emacs-master") RET
M-& git checkout tmp-ed33337c3e0d0b1a8b140e23168421ea43d79324 RET
M-& make RET

M-& ls -l $(which emacs)
lrwxrwxrwx 1 calancha calancha 42 Mar 14 11:11 /home/calancha/bin/emacs -> /home/calancha/soft/emacs-master/src/emacs
M-& emacs -Q ; Same error again.
M-& src/emacs -Q ; OK

Re: Modified remote file name syntax

[Michael Albinus]

Tino Calancha <tino.calancha@gmail.com> writes:

>> It seems also to me, that /usr/local/share/emacs/26.0.50/lisp should not
>> be in game. I suppose, that you haven't run "make install" yet;
> That's right, i didn't run "make install".  Everything is under:
> ~/soft/emacs-master
>
> $> ls -l /usr/local/share/emacs/
> total 12
> drwxrwsr-x 3 root staff 4096 Feb  2 17:09 24.5
> drwxrwsr-x 3 root staff 4096 Feb 26 13:48 25.1
> drwxrwsr-x 2 root staff 4096 May 30  2016 site-lisp
> ;; There is no 26.1 as expected.

Of course. The error speaks about 26.0.50.

Best regards, Michael.

Re: Modified remote file name syntax

[Tino Calancha]

On Tue, 14 Mar 2017, Michael Albinus wrote:

> Tino Calancha <tino.calancha@gmail.com> writes:
>
>>> It seems also to me, that /usr/local/share/emacs/26.0.50/lisp should not
>>> be in game. I suppose, that you haven't run "make install" yet;
>> That's right, i didn't run "make install".  Everything is under:
>> ~/soft/emacs-master
>>
>> $> ls -l /usr/local/share/emacs/
>> total 12
>> drwxrwsr-x 3 root staff 4096 Feb  2 17:09 24.5
>> drwxrwsr-x 3 root staff 4096 Feb 26 13:48 25.1
>> drwxrwsr-x 2 root staff 4096 May 30  2016 site-lisp
>> ;; There is no 26.1 as expected.
>
> Of course. The error speaks about 26.0.50.
>
> Best regards, Michael.
Hi Michael,
after your last commit (5a64d78854998c2ed6d9b8de1b593d8462b8fa39)
everything is OK.  No more issue.
Thank you very much.

Re: Modified remote file name syntax

[Michael Albinus]

Tino Calancha <tino.calancha@gmail.com> writes:

> Hi Michael,

Hi Tino,

> after your last commit (5a64d78854998c2ed6d9b8de1b593d8462b8fa39)
> everything is OK.  The issue is gone :-)

Oops. My commits from today are unrelated to your problem. I believe.

> It seems we can close the X-file.

Yes, PLEASE. I hope the problem doesn't reoccur, after closing the file.

Best regards, Fox Mulder.

Re: Modified remote file name syntax

[Tino Calancha]

On Tue, 14 Mar 2017, Michael Albinus wrote:

> Tino Calancha <tino.calancha@gmail.com> writes:
>
>> Hi Michael,
>
> Hi Tino,
>
>> after your last commit (5a64d78854998c2ed6d9b8de1b593d8462b8fa39)
>> everything is OK.  The issue is gone :-)
>
> Oops. My commits from today are unrelated to your problem. I believe.
I want to believe.
>> It seems we can close the X-file.
>
> Yes, PLEASE. I hope the problem doesn't reoccur, after closing the file.
I confirm it doesn't occur anymore!
> Best regards, Fox Mulder.
The truth is out there.