From: martin rudalics <rudalics@gmx.at>
To: rms@gnu.org
Cc: miles@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: C-u prefix behavior of TAB broken
Date: Sat, 22 Dec 2007 23:08:44 +0100 [thread overview]
Message-ID: <476D8AEC.4050604@gmx.at> (raw)
In-Reply-To: <E1J6BZk-0000cJ-RK@fencepost.gnu.org>
> FWIW all indent-line-functions with the exception of `lisp-indent-line'
> either don't have arguments or, like `c-indent-line', `f90-indent-line',
> and `(c)perl-indent-line' expect completely different arguments here.
> Hence a generic solution seems hardly practicable.
>
> Could you name one or two, so I can take a look and see specifically what
> you mean?
I meant that
(defun lisp-indent-line (&optional whole-exp)
takes one optional argument `whole-exp' that implements the feature.
(defun c-indent-line (&optional syntax quiet ignore-point-pos)
takes three completely unrelated arguments and won't implement the
feature.
(defun python-indent-line ()
takes no argument at all and won't implement the feature either.
All this based on the assumption that `indent-for-tab-command' with a
prefix argument would pass something like `whole-exp' down to the
indent-line function of the major mode and have the latter do the job.
Miles elegantly side-stepped the issue in his patch by implementing the
feature within `indent-for-tab-command' so my argument is void.
next prev parent reply other threads:[~2007-12-22 22:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 22:07 C-u prefix behavior of TAB broken Miles Bader
2007-12-17 12:48 ` martin rudalics
2007-12-17 14:27 ` Miles Bader
2007-12-17 19:03 ` martin rudalics
2007-12-21 0:20 ` Stefan Monnier
2007-12-21 19:49 ` Richard Stallman
2007-12-22 0:11 ` Miles Bader
2007-12-22 9:28 ` martin rudalics
2007-12-22 13:48 ` Miles Bader
2007-12-22 17:41 ` martin rudalics
2007-12-22 19:52 ` Miles Bader
2007-12-22 22:35 ` martin rudalics
2007-12-22 22:59 ` Miles Bader
2008-02-24 19:05 ` Juri Linkov
2008-02-24 19:26 ` Miles Bader
2008-02-24 19:40 ` Juri Linkov
2008-02-25 2:56 ` Miles Bader
2007-12-23 0:55 ` Stefan Monnier
2007-12-23 1:39 ` Miles Bader
2007-12-23 21:49 ` Stefan Monnier
2007-12-22 21:08 ` Richard Stallman
2007-12-22 22:08 ` martin rudalics [this message]
2007-12-23 21:11 ` Richard Stallman
2007-12-23 21:44 ` martin rudalics
2007-12-24 21:55 ` Richard Stallman
2007-12-24 22:33 ` martin rudalics
2007-12-26 5:29 ` Richard Stallman
2007-12-26 13:49 ` Vinicius Jose Latorre
2007-12-26 21:26 ` Richard Stallman
2007-12-27 20:19 ` Juri Linkov
2007-12-28 13:55 ` Richard Stallman
2007-12-28 13:55 ` Richard Stallman
2008-01-03 21:52 ` Juri Linkov
2008-01-03 23:50 ` Miles Bader
2007-12-23 0:51 ` Stefan Monnier
2007-12-23 9:13 ` martin rudalics
2007-12-26 3:00 ` Miles Bader
2007-12-18 2:24 ` Richard Stallman
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=476D8AEC.4050604@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).