From: Dan Espen <despen@verizon.net>
To: help-gnu-emacs@gnu.org
Subject: Re: compile buffer: hide/collapse displayed file paths?
Date: Sun, 30 Jun 2013 13:12:29 -0400 [thread overview]
Message-ID: <icvc4v7caq.fsf@home.home> (raw)
In-Reply-To: mailman.2854.1372611954.22516.help-gnu-emacs@gnu.org
Grant Edwards <grant.b.edwards@gmail.com> writes:
> On 2013-06-29, Peter Dyballa <Peter_Dyballa@Web.DE> wrote:
>>
>> Am 29.06.2013 um 01:05 schrieb Grant Edwards:
>>
>>> Is there any way to collapse/hide the file paths being shown in the
>>> compiler buffer window so that I can see the compiler error/warning
>>> messages without all the keyboard gymanstics?
>>
>> The variable truncate-lines could be involved. I have not set it and
>> I don't see any truncated lines.
>
> I don't really want the lines wrapped (which is what happens when you
> unset truncate-lines). I'd like the errors to remain one-per-line,
> but I want to hide the long path info that I don't care about (emacs
> has opened the file and moved the cursor to the right source line, so
> there's no need for me to see the file's path in the compile buffer
> window).
Did you explain why you have long paths?
Are your Makefiles using full paths?
I used to have a few Makefiles like that and I decided it was not a good
idea.
--
Dan Espen
next prev parent reply other threads:[~2013-06-30 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 23:05 compile buffer: hide/collapse displayed file paths? Grant Edwards
2013-06-29 9:13 ` Peter Dyballa
2013-06-30 17:05 ` Grant Edwards
[not found] ` <mailman.2854.1372611954.22516.help-gnu-emacs@gnu.org>
2013-06-30 17:12 ` Dan Espen [this message]
2013-07-01 13:55 ` Grant Edwards
[not found] ` <mailman.2895.1372686955.22516.help-gnu-emacs@gnu.org>
2013-07-01 19:27 ` Dan Espen
2013-06-29 12:36 ` Thien-Thi Nguyen
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=icvc4v7caq.fsf@home.home \
--to=despen@verizon.net \
--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.
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.