From: Chris Moore <dooglus@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer]
Date: Mon, 08 Jan 2007 14:43:03 +0100 [thread overview]
Message-ID: <m264bheis8.fsf@gmail.com> (raw)
In-Reply-To: <E1H3n7l-0003vg-Tt@fencepost.gnu.org> (Richard Stallman's message of "Mon\, 08 Jan 2007 00\:32\:45 -0500")
Richard Stallman <rms@gnu.org> writes:
> [I sent this message twice but did not get a response.]
I responded before you sent either of them.
> If the compilation buffer begins with error lines right at the top:
Compilation buffers don't begin with error lines. They begin like
this:
-*- mode: compilation; default-directory: "~/" -*-
Compilation started at Mon Jan 8 14:08:26
and they are read-only, too, so I'd have to go out of my way to make
them start with an error line.
On other news: Python-mode can't parse C code and dired doesn't work
if the dired buffer doesn't contain a directory listing.
next prev parent reply other threads:[~2007-01-08 13:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 5:32 [lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer] Richard Stallman
2007-01-08 7:59 ` Jan Djärv
2007-01-08 8:35 ` Nick Roberts
2007-01-08 9:05 ` Jan Djärv
2007-01-08 11:11 ` Lennart Borgman (gmail)
2007-01-08 14:22 ` Jan Djärv
2007-01-08 14:35 ` Lennart Borgman (gmail)
2007-01-08 15:15 ` Stefan Monnier
2007-01-08 17:37 ` Jan Djärv
2007-01-09 0:01 ` Richard Stallman
2007-01-08 15:14 ` Bug reporting (was: [lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer]) Stefan Monnier
2007-01-08 17:26 ` Bug reporting Lennart Borgman (gmail)
2007-01-11 4:05 ` [lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer] Nick Roberts
2007-01-18 21:33 ` Nick Roberts
2007-01-09 0:00 ` Richard Stallman
2007-01-09 1:27 ` Nick Roberts
2007-01-08 13:43 ` Chris Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-31 22:13 Richard Stallman
2006-12-25 0:42 Richard Stallman
2006-12-17 5:37 Richard Stallman
2007-01-19 2:33 ` Chong Yidong
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=m264bheis8.fsf@gmail.com \
--to=dooglus@gmail.com \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.