9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: theinicke@bss-wf.de
To: 9fans@9fans.net
Subject: Re: [9fans] [PATCH] Spaceindent mode for acme
Date: Fri, 06 Aug 2021 19:15:09 +0200	[thread overview]
Message-ID: <16B82B1DBE7071E8D7DE10B054D3179E@bss-wf.de> (raw)
In-Reply-To: <CA+cCjXp3EQ3b6V9P5qA6XBaY=u7tC=x63boSWDYYLBdrShNm+w@mail.gmail.com>

Quoth Rodrigo G. López <rodrigosloop@gmail.com>:
> hi,
> 
> 9front's had this for a long time (last time i used acme it already
> did, back in 2017).
> maybe you could try to import those changes instead of rolling your own?
> 
> 
> best,
> 
> -rodri
> 
> On Thu, Aug 5, 2021 at 6:59 PM binarycat <dogedoge61@gmail.com> wrote:
> > 
> > I do prefer tabs over spaces, but sometimes you have to use spaces.
> > For example, zig doesn't even allow the tab charachter in its source
> > code.
> > 
> > So, I put together a simple patch that adds a command `Spaceindent`.
> > This command works similar to `Indent`, but changing whether to insert
> > tabs or spaces. there is also the `-s` option to enable it on startup.
> > 
> > The number of spaces to insert is the same as the tab width,
> > controlled by `Tab`.
> > 
> > My implementation may be a bit awkward, I haven't tried modifying acme
> > to this extent before.
> > --
> > binarycat <dogedoge61@gmail.com>

FYI: The relevant (git) commit in 9front is 4757debd0b5935dae94944c35c3cac74b14aa209

Note however that this was already ported and a merge request (#192) was issued, but got turned down:
https://github.com/9fans/plan9port/pull/192

--
Tobias Heinicke


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td96032ea2eda50a5-M759f0691883412c54c190d12
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

      reply	other threads:[~2021-08-06 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 16:59 binarycat
2021-08-05 17:28 ` Rodrigo G. López
2021-08-06 17:15   ` theinicke [this message]

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=16B82B1DBE7071E8D7DE10B054D3179E@bss-wf.de \
    --to=theinicke@bss-wf.de \
    --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).