Re: [unicode-2] whitespace-auto-cleanup always replaces leading spaces with tabs

[Braden McDaniel]

On Wed, 2007-04-11 at 23:23 +0200, martin rudalics wrote:
>  > I set it in custom-set-variables; another likely scenario, I would think.
> 
> whitespace.el has this form
> 
> (defcustom whitespace-check-indent-whitespace indent-tabs-mode
> 
> which, as Miles explained, gets evaluated when whitespace is loaded with
> the value `indent-tabs-mode' has at that time.  Apparently you set
> `indent-tabs-mode' to a different value afterwards.  Hence, the values
> of `indent-tabs-mode' and `whitespace-check-indent-whitespace'
> eventually conflict in one of your buffers.  I just wanted to know your
> particular usage pattern in order to propose a solution.

As I said, I normally set these variables in custom-set-variables
(in .emacs).

>  > With regard to your request, I'm unfamiliar with -Q and so far I haven't
>  > found documentation for it. So, more explicit instructions about what
>  > you'd like me to try would be appreciated.
> 
> -Q is an initial option.  From the Emacs manual:
> 
> `-Q'
> `--quick'
>       Start emacs with minimum customizations.  This is like using `-q'
>       and `--no-site-file', but also disables the startup screen.

If I start with -Q and then set whitespace-global-mode to non-nil and
set both whitespace-check-leading-whitespace and
whitespace-check-indent-whitespace to nil, leading sequences of 8 spaces
still get highlighted.

>  >>IMHO there's no reasonable way to reconcile a user's settings of
>  >>`indent-tabs-mode' with those of `whitespace-check-indent-whitespace'. I
>  >>think `whitespace-indent-cleanup' should be executed iff
>  >>`indent-tabs-mode' is non-nil in the current buffer.  But I'm afraid
>  >>that anything we change here will break existing customizations.
>  >
>  >
>  > Why isn't it reasonable for whitespace-indent-cleanup to change tabs in
>  > indentation to spaces when indent-tabs-mode is nil?
> 
> It is reasonable.  Unfortunately, the decisions of
> `whitespace-indent-cleanup' are based on the actual value of
> `whitespace-check-indent-whitespace' and not on that of
> `indent-tabs-mode'.

I see. But I think this has gotten sidetracked from the real bug that
was introduced here. Indeed, the fact that
whitespace-check-indent-whitespace has never done what I want is exactly
the reason I have it set to nil (along with
whitespace-check-leading-whitespace; I'm not clear on how these two
differ).

So the bug that has been introduced recently is whatever causes
whitesapce checking to flag indentation whitespace even though
whitespace-check-indent-whitespace is nil.

-- 
Braden McDaniel                           e-mail: <address@hidden>
<http://endoframe.com>                    Jabber: <address@hidden>