zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: X font completion is buggy
Date: Sun, 26 Jul 2015 14:41:46 -0700	[thread overview]
Message-ID: <150726144146.ZM9170@torch.brasslantern.com> (raw)
In-Reply-To: <20150726211049.GF11938@zira.vinc17.org>

On Jul 26, 11:10pm, Vincent Lefevre wrote:
}
} $ xterm -fn -adobe-helvetica-bold--n--0-0-0-0-p-0-iso8859-[]
} 
} but the cursor shouldn't be at the end because after "bold-",
} there should be i, o or r. If I type [TAB], I get:

If you look at this list, there are three different ways to disambiguate:

} -adobe-helvetica-bold-i-normal--0-0-0-0-p-0-iso8859-1 
} -adobe-helvetica-bold-i-normal--0-0-0-0-p-0-iso8859-2 
} -adobe-helvetica-bold-i-normal--0-0-0-0-p-0-iso8859-15
} -adobe-helvetica-bold-o-narrow--0-0-0-0-p-0-iso8859-1 
} -adobe-helvetica-bold-o-narrow--0-0-0-0-p-0-iso8859-2 
} -adobe-helvetica-bold-o-narrow--0-0-0-0-p-0-iso8859-15
} -adobe-helvetica-bold-o-normal--0-0-0-0-p-0-iso8859-1 
} -adobe-helvetica-bold-o-normal--0-0-0-0-p-0-iso8859-2 
} -adobe-helvetica-bold-o-normal--0-0-0-0-p-0-iso8859-15
} -adobe-helvetica-bold-r-narrow--0-0-0-0-p-0-iso8859-1 
} -adobe-helvetica-bold-r-narrow--0-0-0-0-p-0-iso8859-2 
} -adobe-helvetica-bold-r-narrow--0-0-0-0-p-0-iso8859-15
} -adobe-helvetica-bold-r-normal--0-0-0-0-p-0-iso8859-1 
} -adobe-helvetica-bold-r-normal--0-0-0-0-p-0-iso8859-2 
} -adobe-helvetica-bold-r-normal--0-0-0-0-p-0-iso8859-15

You can add i/o/r after "bold-" to choose to one of the font styles,
or you can type a/o after "n" to choose the width, or you can type
1 or 2 after "59-" to narrow the character sets.

I believe completion always chooses the point of disambiguation with
the longest common prefix (common to the partial completions, not
common to the full list of matches).  If you then type "2" and hit
TAB, that's no longer ambiguous so the cursor moves back to the "n"
because that is still ambiguous, and then if you type "o" and hit
TAB it moves back yet again.

I think you'll find completion always behaves this way, but it's not
usually the case to have this many positions of ambiguity.


  reply	other threads:[~2015-07-26 21:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 21:49 Vincent Lefevre
2015-07-24 22:50 ` Oliver Kiddle
2015-07-24 23:31   ` Bart Schaefer
2015-07-25  8:30     ` Oliver Kiddle
2015-07-26 21:10       ` Vincent Lefevre
2015-07-26 21:41         ` Bart Schaefer [this message]
2015-07-26 22:29           ` Mikael Magnusson
2015-07-26 23:01           ` Vincent Lefevre
2015-07-27  3:19             ` Bart Schaefer
2015-07-27  5:11               ` Mikael Magnusson
2015-07-27 15:40                 ` Bart Schaefer
2015-07-25  1:28   ` Vincent Lefevre
2015-07-24 23:07 ` Bart Schaefer
2015-07-25  0:47   ` Vincent Lefevre

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=150726144146.ZM9170@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).