Expanding Tabs in Solaris debugger

Expanding Tabs in Solaris debugger

Post by John Boss » Fri, 13 Mar 1998 04:00:00



We use tabs set to 4 in our C source code; however, the Solaris
'de*''s text window pane always interprets the tabs as 8.

Does anyone know if it is possible to apply a filter to the de*
when openning a text file (ie. expand -4) or some other setting?

I've been pouring through the on-line help and man pages but cannot figure it
out.

Any help would be greatly appreciated...

John.

--
John E. Bossom                                     Cognos Inc.
Voice: (613) 738-1338 x3386        O_o             P.O. Box 9707, Stn. T
  FAX: (613) 738-0002             =(  )= Ack!      OTTAWA, ON  K1G 4K9

 
 
 

Expanding Tabs in Solaris debugger

Post by Casper H.S. Dik - Network Security Engine » Sat, 14 Mar 1998 04:00:00


[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]


>We use tabs set to 4 in our C source code; however, the Solaris
>'de*''s text window pane always interprets the tabs as 8.

Tab stops are pretty much defined as being 8 apart.

What you've created are files that can't be read easily with more and
other tools; not just in the de*.

Repent; and use spaces instead of tabs in your source code.
Vi uses ^T for that; you can have other editors do different things.
(Personally, I feel it's abig mistake that vi and others allow changing the
pretty much hardcoded-everywhere-else "a tab is 8" rule)

Quote:>Does anyone know if it is possible to apply a filter to the de*
>when openning a text file (ie. expand -4) or some other setting?

I think you can tell teh de* to use a different file viewer.

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

 
 
 

Expanding Tabs in Solaris debugger

Post by Brian Agne » Sat, 14 Mar 1998 04:00:00


I certainly don't think that a tab stop of 4 is unusual or breaking a
'definition' of how big a tab stop should be.

If you use the Solaris Workshop, I think you can specify the de* viewer as
being your editor eg. vi, and hence your problems are solved.

Brian


> [[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]


> >We use tabs set to 4 in our C source code; however, the Solaris
> >'de*''s text window pane always interprets the tabs as 8.

> Tab stops are pretty much defined as being 8 apart.

> What you've created are files that can't be read easily with more and
> other tools; not just in the de*.

> Repent; and use spaces instead of tabs in your source code.
> Vi uses ^T for that; you can have other editors do different things.
> (Personally, I feel it's abig mistake that vi and others allow changing the
> pretty much hardcoded-everywhere-else "a tab is 8" rule)

> >Does anyone know if it is possible to apply a filter to the de*
> >when openning a text file (ie. expand -4) or some other setting?

> I think you can tell teh de* to use a different file viewer.

> Casper
> --
> Expressed in this posting are my opinions.  They are in no way related
> to opinions held by my employer, Sun Microsystems.
> Statements on Sun products included here are not gospel and may
> be fiction rather than truth.

  vcard.vcf
< 1K Download
 
 
 

1. Script GURUs - a tab is a tab is a tab

I have ascii files created by various people I want to run something
that will look for tabs and based on the tab length convert tabs to the
right number of spaces, however the above people use various tab
lengths and do their indenting a little differently. Does someone out
there have a solution to this type of situation?????


you might have a solution.

Thanks in advance

Jim

2. installupdate question

3. expanding tab

4. Framebuffer updates.

5. vi:Auto-expanding tabs->spaces

6. is there any cost involved in setting up my own news site?

7. howto get tab expand file name

8. emacs20 available!

9. Tabs in SparcWorks Debugger

10. entering tab in vi without using tab key

11. replacing tabs with emulated tabs

12. tab versus tab

13. ALT-TAB bug (ALT-TAB on empty desktop, KDE1.1.2)