From: Oliver Scholz <alkibiades@gmx.de>
Subject: Re: line length control setting
Date: Tue, 11 Nov 2003 14:47:56 +0100 [thread overview]
Message-ID: <87n0b3auxe.fsf@ID-87814.user.dfncis.de> (raw)
In-Reply-To: mailman.3297.1068117967.21628.help-gnu-emacs@gnu.org
Adam Hardy <emacs@cyberspaceroad.com> writes:
> Hi All,
> I am using a brute force method of stopping myself from writing long
> lines of code, using this in my .emacs:
>
> (defun my-dont-insert-after-fill-column (&rest x)
> (when (> (current-column)
> fill-column)
> (delete-char -1)
> (beep)))
>
> (add-hook 'after-change-functions 'my-dont-insert-after-fill-column)
>
> But I discovered this is also acting on the command buffer, so I
> cannot add more than my fill column when doing simple file copies or
> renames or text search & replaces.
Well, you could just check whether the current buffer is the
minibuffer:
(when (and (not (minibufferp))
(> (current-column)
fill-column))
...)
However, for my taste this is a little bit too obnoxious, too. I'd
rather prefer some strong visual indication, like turning all lines
longer than 70 chars into a bright red:
(defface ah-overlong-lines
'((t
(:background "red")))
"Face used to display overlong lines")
(defconst ah-overlong-lines-keywords
'(("^.\\{70,500\\}$" 0 'ah-overlong-lines prepend)))
(font-lock-add-keywords nil ah-overlong-lines-keywords)
I seem to recall that there is some package that does something with
colour. I think with the colour of the cursor. But I don't remember
its name.
Or simply turn auto-fill-mode on. This does also some sort of the
right thing for programming modes (although it is not quite as smart
as I wish it would be).
Oliver
--
21 Brumaire an 212 de la Révolution
Liberté, Egalité, Fraternité!
next prev parent reply other threads:[~2003-11-11 13:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3297.1068117967.21628.help-gnu-emacs@gnu.org>
2003-11-06 15:41 ` line length control setting Jesper Harder
2003-11-06 18:27 ` Kevin Rodgers
2003-11-07 13:57 ` Adam Hardy
2003-11-07 18:40 ` Gareth Rees
2003-11-08 14:47 ` Adam Hardy
[not found] ` <mailman.46.1068306647.2005.help-gnu-emacs@gnu.org>
2003-11-10 18:39 ` Gareth Rees
2003-11-11 11:10 ` Adam Hardy
2003-11-11 11:20 ` Adam Hardy
2003-11-11 13:47 ` Oliver Scholz [this message]
2003-11-13 9:49 ` Adam Hardy
[not found] ` <mailman.28.1068720748.399.help-gnu-emacs@gnu.org>
2003-11-13 12:02 ` Oliver Scholz
2003-11-13 17:01 ` Kevin Rodgers
2003-11-17 13:08 ` Adam Hardy
[not found] ` <mailman.157.1069078348.399.help-gnu-emacs@gnu.org>
2003-11-17 14:56 ` Phillip Lord
2003-12-07 15:29 ` Kai Grossjohann
2003-12-08 9:55 ` Adam Hardy
[not found] ` <mailman.1329.1070881092.399.help-gnu-emacs@gnu.org>
2003-12-08 18:14 ` Johan Bockgård
2003-12-10 12:47 ` Adam Hardy
2003-12-12 11:37 ` Adam Hardy
[not found] ` <mailman.1629.1071232851.399.help-gnu-emacs@gnu.org>
2003-12-12 18:58 ` Johan Bockgård
2003-12-13 11:06 ` Adam Hardy
[not found] ` <mailman.15.1071317460.868.help-gnu-emacs@gnu.org>
2003-12-13 18:13 ` Johan Bockgård
2003-11-06 11:24 Adam Hardy
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=87n0b3auxe.fsf@ID-87814.user.dfncis.de \
--to=alkibiades@gmx.de \
/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).