Re: [joe] "^K ," behavior

[Reuben D. B. <tec...@vo...>]

On Thursday 15 July 2004 10:45, ja...@av... wrote:
> So ^K , and ^K . use indentc and istep (Indent char and indent step in ^T).
>
> If indentc is 32 (space), ^K , and ^K . will convert tabs to spaces if
> necessary to do the indent (which is better than joe2.9.8).  If indentc is
> 9 (tab), ^K , and ^K . require the indenting to be all tabs.

In my config file, I always specify the indenting character to be space.

> Joe-3.1 tries to guess indentc: it searches backwards through the file and
> uses whatever the first indent character it finds.

I suppose turning "guess indent" off would then make joe obey the specified 
indentc ?

> However, one other thing you said I don't think is correct:
>
> "Reuben D. Budiardja" <tec...@vo...> wrote:
> > Hello,
> > Suppose I have a 'messy' text in a file that is not properly indented. In
> > previous version of Joe (eg. 2.9.8), I can select all the text, the do
> > ^K, many times to 'remove' the spaces, or indents for every line, until I
> > hit the left most possible, ie. until there is no indentation or space
> > left on the left side. Of course, some lines get there first if it has
> > less space or indentation to begin with, but eventually all lines will
> > have no indentation. This was a quick way to remove messy spaces /
> > indentation
>
> I don't think 2.9.8 did this: I think it just stopped when the line with
> the least indentation hit the left side.  

Sorry, you were right.

> I'm thinking now that JOE should
> prompt the user when this happens, asking if it should keep going while
> losing indent information.

Yes, that would be good. If my text is 'messy' to begin with, I don't care if 
I loose all the indent information. Then I can start over. 

Thanks.
RDB