From: Dan Espen <despen@verizon.net>
To: help-gnu-emacs@gnu.org
Subject: Re: compile buffer: hide/collapse displayed file paths?
Date: Mon, 01 Jul 2013 15:27:16 -0400 [thread overview]
Message-ID: <icfvvy2i97.fsf@home.home> (raw)
In-Reply-To: mailman.2895.1372686955.22516.help-gnu-emacs@gnu.org
Grant Edwards <grant.b.edwards@gmail.com> writes:
> On 2013-06-30, Dan Espen <despen@verizon.net> wrote:
>> Grant Edwards <grant.b.edwards@gmail.com> writes:
>>
>>> 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?
>
> No, I didn't realize it was relevent to the question.
>
>> Are your Makefiles using full paths?
>
> Yes. The makefiles are auto-generated by an OS build system over which
> I don't have control.
Bummer.
>> I used to have a few Makefiles like that and I decided it was not a
>> good idea.
>
> Perhaps, but in this case, the relative path name from the build
> directory to the source directory would in most cases be even longer
> than the absolute path name.
I'm an advocate for hand crafted Makefiles but I don't suppose you can
do much to change that where you are.
--
Dan Espen
next prev parent reply other threads:[~2013-07-01 19:27 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
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 [this message]
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
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=icfvvy2i97.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.
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).