RE: [Dev-C++] Tabs vs. spaces in the editor -- by design or a bu g? (4.9.9.1)

[Mark S. <mar...@li...>]

Hi
Likewise I've been annoyed at the tab/indenting etc of the editor and as a
work around I've installed astyle http://astyle.sourceforge.net/ as a tool,
this allows you to customise the appearance of your source code at the click
of a button.
mark

-----Original Message-----
From: Len Philpot [mailto:le...@ph...]
Sent: 02 December 2004 23:07
To: dev...@li...
Subject: Re: [Dev-C++] Tabs vs. spaces in the editor -- by design or a
bug? (4.9.9.1)


> I've noticed similar behavior.  If I type the following (text in angle
> brackets are keypresses; everything else is a literal string)...

Is there any way to fix this?

All in all, I really like Dev-C++, in fact, I am lately using it more 
than Visual Studio .NET (much easier to use), but this editor 
malfunction is a major irritant. I've been tempted to use MinGW 
DevStudio, except that it's apparently been abandoned. It's editor 
indents/aligns properly.

Is this a feature/bug/characteristic of Synedit or is it how it's 
configured in Dev-C++?

I'd be perfectly happy if I could just make it insert one tab each 
time I hit Tab, insert enough tabs to align with the first non-
whitespace character on the previous line, insert (only) spaces or 
tabs as directed and be able to turn "Auto Align" off when desired. 
As is, I spend easily a good third of my time undoing what it does, 
needlessly backspacing around, re-indenting, etc.

-- 
 Len Philpot                          ><> 
 le...@ph...       http://philpot.org/


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.289 / Virus Database: 265.4.4 - Release Date: 30/11/2004
 


The information contained in this e-mail message (and any attachment
transmitted herewith) is privileged and confidential and is intended for the
exclusive use of the addressee(s). If you are not an addressee, any
disclosure, reproduction, distribution or other dissemination or use of this
communication is strictly prohibited. If you have received this
communication in error, please contact us immediately so that we can correct
the error.