Ticket #2871 (closed defect: fixed)

Opened 17 months ago

Last modified 17 months ago

#367405: command-line completion backspaces instead

Reported by: myon Owned by: me
Priority: minor Milestone: 1.6
Component: mutt Version:
Keywords: Cc: 367405@…

Description (last modified by brendan) (diff)

Hi,

the following was submitted as Debian bug #367405:


Date: Mon, 15 May 2006 14:37:40 -0400
From: Chung-chieh Shan <ken@digitas.harvard.edu>
Reply-To: Chung-chieh Shan <ken@digitas.harvard.edu>,
	367405@bugs.debian.org
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#367405: mutt: command-line completion backspaces instead

Hello,

When I type "|cat >/usr/local/bi" at Mutt's index screen and hit Tab, I expect Mutt to add "n" or "n/" to the command line. Instead, it removes "/bi" from the command line. (To reproduce this bug, there must be no space after ">".)

Thanks,

Ken


Christoph

Change History

Changed 17 months ago by me

  • owner changed from mutt-dev to me
  • priority changed from major to minor
  • description modified (diff)
  • milestone set to 1.6

Changed 17 months ago by me

  • cc 367405@… added

I have confirmed this behavior and will fix it. There seem to be two problems: 1) the complete function in _mutt_enter_string() looks backward for the first space character, which means in the input used in the bug report, the greater-than symbol is included in the pathname, and 2) mutt_complete() destructively alters the string even if it can't complete the pathname.

Changed 17 months ago by me

Changeset [83440e7b2e52] fixes part of this problem. The trailing component of the pathname is no longer removed. Completion still does not work, but that will be addressed in a separate changeset.

Changed 17 months ago by brendan

  • description modified (diff)

Changed 17 months ago by me

  • status changed from new to closed
  • resolution set to fixed

[097deb080af0] changes the "complete" function to consider shell characters as word boundaries (previously only space was considered as such).

Note: See TracTickets for help on using tickets.