ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] tab-width considered less effective than some might think

From: Bill Meier <wmeier@xxxxxxxxxxx>
Date: Thu, 23 Jul 2009 21:56:02 -0400
Guy Harris wrote:

<snip>

At least on UN*X, it's probably best to assume that a tab character in a file advances to the next tab stop, with tab stops set every 8 characters. Yes, this means that if you want 4-space indents, you can't use tab characters, although it might be possible to configure your editor so that typing the tab key indents every 2, or 4, or... spaces, e.g. by setting c-basic-offset to 4 in GNU Emacs.


I suspect we're on the same page.

My personal preference is to use only spaces for indentation and that, if tabs are used, the tab stops should be every 8 characters.

IOW I agree, as you suggest, that if tabs are used "it's probably best to assume ..., with tab stops at every 8 characters".

Another example: I note that viewvc assumes (or is configured to assume) 8 character tabs stops when displaying Wireshark source
(http://anonsvn.wireshark.org/viewvc).

I've been thinking for quite some time about suggesting that the use "non 8 space tabs" (eg: tab stops every 4 spaces) be deprecated;

So: what do others think ?  :)