unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Aymeric Agon-Rambosson <aymeric.agon@yandex.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67158@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#67158: [PATCH] Repair tab-always-indent
Date: Wed, 15 Nov 2023 01:24:04 +0100	[thread overview]
Message-ID: <87cywbrhi3.fsf@X570GP> (raw)
In-Reply-To: <837cmktsou.fsf@gnu.org>


Le mardi 14 novembre 2023 à 14:39, Eli Zaretskii <eliz@gnu.org> a 
écrit :

> Could you please post a recipe which reproduces the problems you
> describe?

With emacs -Q.

On the scratch buffer (lisp-interaction-mode), eval the following 
lines :

(setq tab-always-indent 'complete)
(setq tab-first-completion 'word)

Then type "tty" (without the quotes) on an empty line, place point 
on the "y", and evaluate '(syntax-after (point))'.

You get "(2)" in the minibuffer, which is proof you are in the 
middle of a word according to the syntax table.

Then, with the point still on the "y", press TAB (or evaluate 
'(indent-for-tab-command)').

"tty" gets autocompleted to "tty-" and the point is placed after 
the "-".

This is in contradiction with what the docstring says about the 
variable tab-first-completion.

This is also reproducible if you set tab-first-completion to 
either 'word-or-paren or 'word-or-paren-or-punct.

A detailed explanation of what causes this can be found in my 
previous mail. Feel free to ask any questions.

The problem is not reproducible anymore with the patch applied.

Best,

Aymeric






  reply	other threads:[~2023-11-15  0:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 23:43 bug#67158: [PATCH] Repair tab-always-indent Aymeric Agon-Rambosson
2023-11-14 12:39 ` Eli Zaretskii
2023-11-15  0:24   ` Aymeric Agon-Rambosson [this message]
2023-11-25  9:31 ` Eli Zaretskii
2023-11-25 15:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-26  9:42   ` Aymeric Agon-Rambosson
2023-11-26 13:56     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-29 14:25       ` Eli Zaretskii

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=87cywbrhi3.fsf@X570GP \
    --to=aymeric.agon@yandex.com \
    --cc=67158@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).