On 26 Jun 2002 12:18:19 +0200, Dominik Vogt wrote: > > > > Ooops this is a bit dangerous as in some strings which have to be > > > displayed in an X window spaces should not be replaced by a tab. > > I hope we have none such strings.
Sorry, but we have a lot of such strings. XError.c, ewmh.c, fvwm.c, session.c, stack.c, FvwmIdent.c and so on. > > It's not only strings; statements and comments are now full of TABs. > > Hm, statements and comments? They shouldn't have more than a > single space anywhere. When I come across any in-line formatting > I remove that anyway. The way I format code, tabifying it is > completely safe. Every GPL header now contains 2 TABs. Take a look at your paragraph above, 3 double spaces. tabify would replace some of them with TAB, then adding "> " prefix would make the quote strewn. Diffs (with a leading "+" prefix) look strewn on lines with TAB in the middle. Unless tabify may be configured to only handle leading spaces, it is not suitable for an automatic replacement. > > I would not use the emacs's tabify, TABs in the middle of line are bad. I will fix this in several minutes. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
