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

2009-07-27 Thread Gerald Combs
Bill Meier wrote: Gerald Combs wrote: Visual C++ defaults to tabs for indentation with tab stops every 4 characters. I'm not sure if these settings can be overridden without changing the user's global preferences. I'm not sure as to your exact concerns. Poking around a bit in VS2008 I

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

2009-07-27 Thread Bill Meier
Gerald Combs wrote: Gerald Combs wrote: Visual C++ defaults to tabs for indentation with tab stops every 4 characters. I'm not sure if these settings can be overridden without changing the user's global preferences. snip I'm assuming that these settings are global since there doesn't

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

2009-07-25 Thread Bill Meier
Gerald Combs wrote: Visual C++ defaults to tabs for indentation with tab stops every 4 characters. I'm not sure if these settings can be overridden without changing the user's global preferences. I'm not sure as to your exact concerns. Poking around a bit in VS2008 I see the following

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

2009-07-24 Thread Gerald Combs
Bill Meier wrote: 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). It looks like Viewvc just dumps everything into a pre/pre container and lets the browser decide. I've

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

2009-07-24 Thread Guy Harris
On Jul 24, 2009, at 8:44 AM, Gerald Combs wrote: Visual C++ defaults to tabs for indentation with tab stops every 4 characters. I'm not sure if these settings can be overridden without changing the user's global preferences. Then perhaps the answer is indent with space characters, not tab

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

2009-07-23 Thread Guy Harris
The tab-width GNU Emacs mode appears to affect what a tab character in a file does; to quote the GNU Emacs manual: Some ASCII control characters are displayed in special ways. The newline character (octal code 012) is displayed by starting a new line. The tab character (octal code 011)

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

2009-07-23 Thread Jaap Keuter
Hi, Sent from my iPhone On 24 jul 2009, at 03:56, Bill Meier wme...@newsguy.com wrote: 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

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

2009-07-23 Thread Sake Blok
On Thu, Jul 23, 2009 at 09:56:02PM -0400, Bill Meier wrote: 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 ? :) I would go one step further, as tabs will be displayed differently

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

2009-07-23 Thread Sake Blok
On Fri, Jul 24, 2009 at 07:35:49AM +0200, Sake Blok wrote: On Thu, Jul 23, 2009 at 09:56:02PM -0400, Bill Meier wrote: 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 ? :)