GNU bug report logs - #34787
New defcustom to govern TAB completion

Previous Next

Full log

View this message in rfc822 format

From: Stefan Kangas <stefan <at> marxist.se>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 34787 <at> debbugs.gnu.org, Alex Branham <alex.branham <at> gmail.com>
Subject: bug#34787: New defcustom to govern TAB completion
Date: Mon, 24 Aug 2020 12:22:20 -0700

Noam Postavsky <npostavs <at> gmail.com> writes:

> Alex Branham <alex.branham <at> gmail.com> writes:
>
>> On Sat 25 May 2019 at 08:37, Noam Postavsky <npostavs <at> gmail.com> wrote:
>>
>>> Alex Branham <alex.branham <at> gmail.com> writes:
>>>
>>>> As a quick reminder/TLDR - the proposal is to add a defcustom that
>>>> governs whether TAB offers completion when hit the first time. The
>>>> thinking is that if point is in the middle of a word, you may not want
>>>> completion.
>>>
>>> How would it interact with the existing tab-always-indent?  Would it
>>> make sense to combine them?
>>
>> The way we have it in ESS currently is that they're two separate
>> variables. One (our version of tab-always-indent) governs whether TAB
>> offers completion and another (what I'm proposing adding to Emacs)
>> governs whether the first press of TAB should offer completion based on
>> context.
>
> Oh, I see, it only affects people who have already customized
> tab-always-indent to a non-default value (specifically, `complete').
>
> So I guess the idea is that (setq tab-always-indent 'complete) triggers
> too many accidental completions to be a reasonable setting?  I think it
> would be nicer if the option's values could be `(word paren)', `(word
> paren punct) instead of `word-or-paren', `word-or-paren-or-punct', etc.

(That was one year ago.)

Are you still working on this?

Best regards,
Stefan Kangas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.