From: Dan Nicolaescu <dann@ics.uci.edu>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: compilation-mode needs a tool-bar
Date: Mon, 25 Feb 2008 09:06:47 -0800 [thread overview]
Message-ID: <200802251706.m1PH6lTL018076@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <47C29EDE.5090202@swipnet.se> ("Jan Djärv"'s message of "Mon, 25 Feb 2008 11:56:30 +0100")
Jan Djärv <jan.h.d@swipnet.se> writes:
> Dan Nicolaescu skrev:
> > Jan Djärv <jan.h.d@swipnet.se> writes:
> >
> > > And having them in the tool bar for the *compilation* buffer is not
> > > a big help as I imagine most do like me and are seldom in that
> > > buffer anyway.
> >
> > Disagree. I spend a fair amount of time in the *grep* buffer, finding
> > the exact thing I was looking for. The same is true for compilation,
> > some tools produce hard to understand errors, so one needs to stair at
> > them for a bit to figure out what is going on.
> >
>
> Well, I don't mind having more buttons for that mode, so I added
> next/previous error, stop and recompile to compilation and grep mode.
> The choice and order of the icons can as always be discussed and
> changed.
Thanks! Don't the arrow icons (prev/next) usually point away from each
other? Maybe those two can be swapped.
BTW, if you have interest, there's a few more places that could use a
tool-bar (not sure if standard icons exist for those actions to make
adding a tool-bar easy):
- vc-status
- smerge-mode
- ediff-directories (this one could use a menu even more than a tool-bar)
next prev parent reply other threads:[~2008-02-25 17:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 3:16 compilation-mode needs a tool-bar Dan Nicolaescu
2008-02-25 4:42 ` Nick Roberts
2008-02-26 2:00 ` Xavier Maillard
2008-02-25 7:14 ` Jan Djärv
2008-02-25 8:21 ` Dan Nicolaescu
2008-02-25 10:56 ` Jan Djärv
2008-02-25 17:06 ` Dan Nicolaescu [this message]
2008-02-26 7:07 ` Jan Djärv
2008-02-26 18:14 ` Dan Nicolaescu
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=200802251706.m1PH6lTL018076@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
/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.