bug#38192: [26.3] A problem with indentation on Whitespace minor mode

bug#38192: [26.3] A problem with indentation on Whitespace minor mode

[libr3]

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]

There is a little problem, I guess that is by confusion, with two indentation functions.

If we use this:
(setq whitespace-style (quote (indentation::space)))
in our configuration file on GNU Emacs (.emacs or init.el), we'll have the expected result for the next function:
 (setq whitespace-style (quote (indentation::tabs)))
The same happen but with the inverse case.

On other words, the function used has been exchanged with the other function.

We can to test it too with 
M-x whitespace-toggle-options RET ?
If we look the FACES table, and we had enabled just one aforementioned function, we'll see that the function enabled isn't the function that appear as enabled on the table (for example, if you had enabled indentation::space, it marks as enabled "toggle indentation TABs visualization" instead of the correct.

[-- Attachment #2: Type: text/html, Size: 1521 bytes --]

bug#38192: [26.3] A problem with indentation on Whitespace minor mode

[Stefan Kangas]

libr3 <libr3@tutanota.com> writes:

> There is a little problem, I guess that is by confusion, with two indentation functions.
>
> If we use this:
> (setq whitespace-style (quote (indentation::space)))
> in our configuration file on GNU Emacs (.emacs or init.el), we'll have the expected result for the next function:
> (setq whitespace-style (quote (indentation::tabs)))
> The same happen but with the inverse case.
>
> On other words, the function used has been exchanged with the other function.
>
> We can to test it too with
> M-x whitespace-toggle-options RET ?
> If we look the FACES table, and we had enabled just one aforementioned function, we'll see that the function enabled isn't the function
> that appear as enabled on the table (for example, if you had enabled indentation::space, it marks as enabled "toggle indentation TABs
> visualization" instead of the correct.

I'm not sure I understand what you are trying to explain.

Could you please try to restate the problem you are seeing using other
words?

Please provide a step-by-step recipe of how to reproduce the issue,
starting from "emacs -Q".

Best regards,
Stefan Kangas

bug#38192: [26.3] A problem with indentation on Whitespace minor mode

[Bhavin Gandhi]

On Wed, 13 Nov 2019 at 07:57, libr3 <libr3@tutanota.com> wrote:
>
> On other words, the function used has been exchanged with the other function.
>
> We can to test it too with
> M-x whitespace-toggle-options RET ?
> If we look the FACES table, and we had enabled just one aforementioned function, we'll see that the function enabled isn't the function that appear as enabled on the table (for example, if you had enabled indentation::space, it marks as enabled "toggle indentation TABs visualization" instead of the correct.

Are you referring to the same thing which is explained in Bug#22874.
AFAIU, when indentation::space is enabled it highlights TABs and vise versa.

https://debbugs.gnu.org/22874#16

bug#38192: [26.3] A problem with indentation on Whitespace minor mode

[Stefan Kangas]

Bhavin Gandhi <bhavin7392@gmail.com> writes:

> On Wed, 13 Nov 2019 at 07:57, libr3 <libr3@tutanota.com> wrote:
>>
>> On other words, the function used has been exchanged with the other function.
>>
>> We can to test it too with
>> M-x whitespace-toggle-options RET ?
>> If we look the FACES table, and we had enabled just one aforementioned
>> function, we'll see that the function enabled isn't the function that appear
>> as enabled on the table (for example, if you had enabled indentation::space,
>> it marks as enabled "toggle indentation TABs visualization" instead of the
>> correct.
>
> Are you referring to the same thing which is explained in Bug#22874.
> AFAIU, when indentation::space is enabled it highlights TABs and vise versa.
>
> https://debbugs.gnu.org/22874#16

No further information has been provided within 13 weeks, so I'm going
to assume yes, and I'm closing this bug.

If this conclusion is incorrect and this is still an issue, please reply
to this email (use "Reply to all" in your email client) and we can
reopen the bug report.