[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-AUCTeX] [RFH] Debian reported upstream bugs

From: Tassilo Horn
Subject: Re: [Bug-AUCTeX] [RFH] Debian reported upstream bugs
Date: Mon, 03 Nov 2014 13:24:54 +0100
User-agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux)

David Kastrup <address@hidden> writes:

[Sorry if that's a duplicate.]

>> So how about always using `TeX-read-string' and have a new option
>> `TeX-read-string-inherit-input-method'?  Next to nil/non-nil we could
>> allow (lambda (prompt) ...) as a value, so users even had the chance
>> to say "Don't inherit input method when reading
>> sizes/positions/dates, etc." (assuming the prompts are informative
>> enough).
> I don't see that this will magically buy us the consistency that
> currently appears lacking.

With a boolean value of `TeX-read-string-inherit-input-method' the input
method is either always inherited or never inherited.  To me that's
consistent.  With a lambda as a value, any inconsistencies are defined
by the user.

I think users can judge much better if and where they want to inherit
the current input method than we can.  After all, that depends on the
current input method, the keyboard layout, the default input method,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]