ls quoting style change requires Emacs tramp pkg update

Bug #1774798 reported by Bob Givan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
emacs25 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Emacs 26 provides the following bug fix to Emacs 25:

https://github.com/emacs-mirror/emacs/commit/e4adb6

which fixes the dired/tramp/ls interaction bug introduced by the "new" quoting style in ls:

https://lists.gnu.org/archive/html/bug-coreutils/2016-03/msg00032.html

Because 18.04 LTS provides Emacs25 without this fix, BUT provides ls with the new quoting-style default, Emacs dired-mode breaks when used over tramp, if filenames and directories contain spaces.

The easy bug fix above should be retroactively applied to the version of Emacs/tramp that is being provided. Alternatively, Emacs 26 could be provided, or Tramp updated to 2.3.2 provided within Emacs25.

Specifically, remote directories listed using dired over tramp show files and directories (those with spaces in the names) that cannot be acted upon by dired commands but instead complain that the listing is out of date and needs updating, even if updated.

The two line fix cited above resolves the problem in my installation.

Release: 18.04 LTS

apt-cache policy emacs25
emacs25:
  Installed: 25.2+1-6
  Candidate: 25.2+1-6
  Version table:
 *** 25.2+1-6 500
        500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: emacs25 25.2+1-6
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 2 12:08:03 2018
ExecutablePath: /usr/bin/emacs25-x
InstallationDate: Installed on 2018-05-12 (20 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: emacs25
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Bob Givan (givan-q) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.