From: David Kastrup <dak@gnu.org>
Subject: Code cleanup.
Date: Mon, 23 Oct 2006 13:55:19 +0200 [thread overview]
Message-ID: <85y7r7l00o.fsf@lola.goethe.zz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]
Hi,
in the course of checking the code for call-interactively (I have a
tendency to read code rather than the documentation), I felt a bit
like coming upon an obfuscated C contest.
I attach a patch (untested though) that does nothing except hopefully
get a more readable code.
Ok, so we are in freeze anyway, so tampering with any code that works
by replacing it with code designed to be completely equivalent is
probably not worth the potential trouble.
At what stage of development (if at all) should such janitorial
changes be usually applied?
And are there others that would agree with my assessment concerning
the readability here, or that would have even better ideas how this
would be expressed more obvious?
On a completely different tangent: wouldn't it be much more readable
(though likely not completely correct in some perverse manner) if
diff-mode actually had its TAB positions in column 9,17,25... instead
of the customary 8,16,24...? At least in context and unified diffs,
that would _much_ better reflect the relative indentation of the
actual change than the current behavior.
It does not look like `tab-width' can be made to do that, but maybe
one could use a display property in order to move the information of
column 0 into the fringe.
But it would probably be saner if tab-width were extended to allow,
say, a cons-cell of initial offset and tab-width.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1013 bytes --]
*** callint.c 19 Oct 2006 21:07:18 +0200 1.148
--- callint.c 23 Oct 2006 13:30:50 +0200
***************
*** 473,488 ****
/* Count the number of arguments the interactive spec would have
us give to the function. */
tem = string;
! for (j = 0; *tem; j++)
{
/* 'r' specifications ("point and mark as 2 numeric args")
produce *two* arguments. */
! if (*tem == 'r') j++;
tem = (unsigned char *) index (tem, '\n');
if (tem)
! tem++;
else
! tem = (unsigned char *) "";
}
count = j;
--- 473,491 ----
/* Count the number of arguments the interactive spec would have
us give to the function. */
tem = string;
! for (j = 0; *tem;)
{
/* 'r' specifications ("point and mark as 2 numeric args")
produce *two* arguments. */
! if (*tem == 'r')
! j += 2;
! else
! j++;
tem = (unsigned char *) index (tem, '\n');
if (tem)
! ++tem;
else
! break;
}
count = j;
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2006-10-23 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 11:55 David Kastrup [this message]
2006-10-23 16:50 ` Code cleanup Kim F. Storm
2006-10-23 17:29 ` David Kastrup
2006-10-23 18:03 ` David Kastrup
2006-10-23 19:35 ` Stefan Monnier
2006-10-25 18:03 ` Richard Stallman
2006-10-25 19:01 ` David Kastrup
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=85y7r7l00o.fsf@lola.goethe.zz \
--to=dak@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).