9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Nemo <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] tabstops
Date: Fri, 16 Nov 2012 12:58:05 +0100	[thread overview]
Message-ID: <9614EC32-AF16-40EA-838D-AFB7B2D1BA50@lsub.org> (raw)
In-Reply-To: <676562224.kVajVNqNgl@coil>

or a script that does everything for you. 
you edit at one tree and Rin the script
which copies to another replaces and submits. 

On Nov 16, 2012, at 12:37 PM, dexen deVries <dexen.devries@gmail.com> wrote:

> On Friday 16 of November 2012 11:12:38 Steve Simon wrote:
>> I am working on a project that insists on 4 space indentation of code.
>> 
>> I can change the tabstop environment variable so I layout the code
>> how they want but I am still inderting tabs into my source.
>> 
>> I can use russ's tab(1) to convert the tabs to whitespace before every
>> checkin, but thats a bit painful.
> 
> create tabfs, a stacking FS? convert leading tabs to spaces on write(3), 
> convert leading quartets of spaces to tabs on read(3).
> 
> IIRC there was already some stacking FS doing somet ranslation, perhaps it was 
> CRLF <->LF
> 
> -- 
> dexen deVries
> 
> [[[↓][→]]]
> 
> 
> Reality is just a convenient measure of complexity.
>                -- Alvy Ray Smith



  reply	other threads:[~2012-11-16 11:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 11:12 Steve Simon
2012-11-16 11:37 ` dexen deVries
2012-11-16 11:58   ` Nemo [this message]
2012-11-16 12:11     ` lucio
2012-11-16 12:09 ` lucio
2012-11-16 13:12 ` Juan Fuentes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9614EC32-AF16-40EA-838D-AFB7B2D1BA50@lsub.org \
    --to=nemo@lsub.org \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).