unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: philip@warpmail.net (Philip K.)
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 41408@debbugs.gnu.org
Subject: bug#41408: Add a project-compile command
Date: Tue, 19 May 2020 22:07:08 +0200	[thread overview]
Message-ID: <878shnvgcz.fsf@bulbul> (raw)
In-Reply-To: <c842409b-a94e-0da0-8800-211bc52eafd7@yandex.ru> (message from Dmitry Gutov on Tue, 19 May 2020 22:59:07 +0300)

Dmitry Gutov <dgutov@yandex.ru> writes:

> Hey Philip,
>
> On 19.05.2020 21:24, Philip K. wrote:
>> this patch adds a `compile' command for project.el. It's nothing fancy,
>> just sets the first directory of `project-roots' as `default-directory',
>> and then calls the regular compile.
>> 
>> The TODOs mention a `project-build' command, and from my interpretation,
>> this is a slimmed down version (hence the other name, but also because
>> it just called compile in a different environment).
>
> Is this a command you'd be using yourself? If so, we'll add it happily.

I wrote it because I needed it, otherwise I wouldn't have suggested it,
hoping others to do. And I assume others do, since projectile has a
similar command (projectile-compile-project).

> I'm just asking because it's indeed bare-bones, and I basically never 
> use 'M-x compile' directly.

Hmm, I regularly use compile/recompile, but maybe that's my mistake. If
you don't mind me asking, how do you invoke compile or related
functions? If I'm doing it the "wrong way", maybe it might not be worth
applying this patch.

-- 
	Philip K.





  reply	other threads:[~2020-05-19 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 18:24 bug#41408: Add a project-compile command Philip K.
2020-05-19 19:59 ` Dmitry Gutov
2020-05-19 20:07   ` Philip K. [this message]
2020-05-19 21:55     ` Dmitry Gutov
2020-05-19 22:17     ` Kévin Le Gouguec
2020-05-19 23:02 ` Dmitry Gutov

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=878shnvgcz.fsf@bulbul \
    --to=philip@warpmail.net \
    --cc=41408@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).