unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Elena <egarrulo@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Indenting Emacs Lisp only with tabs?
Date: Thu, 3 Sep 2009 07:02:43 -0700 (PDT)	[thread overview]
Message-ID: <925ebcbc-b458-41ee-8aa7-bc57b97aa06b@e8g2000yqo.googlegroups.com> (raw)
In-Reply-To: mailman.5938.1251980288.2239.help-gnu-emacs@gnu.org

On 3 Set, 12:17, B Smith-Mannschott <bsmith.o...@gmail.com> wrote:
> One of the reasons we stick with monospaced fonts in programming is
> because we like to play all sorts of clever tricks with vertical
> alignment to visually group related things. (These tricks,
> incidentally, are also why mixing tabs and spaces causes so much pain
> much of the time.)

Indeed, what a mode means when it indents a line with N spaces is:
move this text under (N+1)th character of previous line. That could be
accomplished with proportional fonts, too. Modes use spaces for what
they do, not what they mean. That's why I don't think we will anything
like elastic tabstops in Emacs in the near future. Too much indenting
code depends on this low level assumption.

> But, *of course* it requires different habits when laying out code. Of
> course, an editor that supports it as well as emacs does mono-spaced
> layout would include logic to insert hard tabs at the right places to
> produce a pleasing layout, just as emacs inserts spaces to vertically
> align the arguments of a mult-line procedure call.

I think that could be eased by making tabs (that is: vertical
alignment) visible, just as I think modes for makefiles already do
(albeit not for alignment purposes).

> I think it's a clever idea, and I do think I could learn to take
> advantage of what it offers while minimizing the impact of its
> downsides, just as I do now when I code in emacs.

I agree.




  parent reply	other threads:[~2009-09-03 14:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 10:38 Indenting Emacs Lisp only with tabs? Elena
2009-09-02 12:56 ` Peter Dyballa
     [not found] ` <mailman.5848.1251896183.2239.help-gnu-emacs@gnu.org>
2009-09-02 13:11   ` Elena
2009-09-02 13:35     ` Helmut Eller
2009-09-02 13:54       ` Elena
2009-09-02 17:19       ` Oliver Scholz
2009-09-04  5:51         ` Oliver Scholz
2009-09-04  7:37           ` Elena
2009-09-04 10:14             ` Oliver Scholz
2009-09-02 14:06     ` Peter Dyballa
     [not found]     ` <mailman.5856.1251900422.2239.help-gnu-emacs@gnu.org>
2009-09-02 14:25       ` Elena
2009-09-02 15:15         ` Peter Dyballa
     [not found]         ` <mailman.5867.1251904529.2239.help-gnu-emacs@gnu.org>
2009-09-02 15:31           ` Elena
2009-09-02 17:15         ` Helmut Eller
2009-09-03  8:11         ` Joost Kremers
2009-09-03 12:17           ` B Smith-Mannschott
     [not found]           ` <mailman.5938.1251980288.2239.help-gnu-emacs@gnu.org>
2009-09-03 14:02             ` Elena [this message]
2009-09-03 18:46             ` Joost Kremers
2009-09-03 19:05               ` Elena

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=925ebcbc-b458-41ee-8aa7-bc57b97aa06b@e8g2000yqo.googlegroups.com \
    --to=egarrulo@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).