From: Stefan Kangas <stefan@marxist.se>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 34787@debbugs.gnu.org, Alex Branham <alex.branham@gmail.com>
Subject: bug#34787: New defcustom to govern TAB completion
Date: Mon, 24 Aug 2020 12:22:20 -0700 [thread overview]
Message-ID: <CADwFkmn-3V+raMA+L72UAtvLsT2PHfrh5+ABqQezE+8GJDqv7g@mail.gmail.com> (raw)
In-Reply-To: <87y32g3ing.fsf@gmail.com> (Noam Postavsky's message of "Tue, 04 Jun 2019 21:50:11 -0400")
Noam Postavsky <npostavs@gmail.com> writes:
> Alex Branham <alex.branham@gmail.com> writes:
>
>> On Sat 25 May 2019 at 08:37, Noam Postavsky <npostavs@gmail.com> wrote:
>>
>>> Alex Branham <alex.branham@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
prev parent reply other threads:[~2020-08-24 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 18:21 bug#34787: New defcustom to govern TAB completion Alex Branham
2019-03-08 19:29 ` Alex Branham
2020-10-14 5:29 ` Lars Ingebrigtsen
2019-05-25 13:05 ` Alex Branham
2019-05-25 13:37 ` Noam Postavsky
2019-05-25 13:43 ` Alex Branham
2019-06-05 1:50 ` Noam Postavsky
2020-08-24 19:22 ` Stefan Kangas [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmn-3V+raMA+L72UAtvLsT2PHfrh5+ABqQezE+8GJDqv7g@mail.gmail.com \
--to=stefan@marxist.se \
--cc=34787@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
--cc=npostavs@gmail.com \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).