Default compile directory

Default compile directory

[Sumit Narayan]

Hi,

Is there any way to set default compile directory?

The problem: I have a many sub-folders in my project and when I edit a
file deep inside subfolders and do M-x compile, I end up running make
in that subfolder, instead of the root folder. Is there any way for
Emacs to always run compile in the default folder?

One thing I figured was to change default compile command to be: cd
<project's root folder>; make. Is that the only/best way?

Thanks.
Sumit.

Re: Default compile directory

[Ivan Kanis]

> Is there any way to set default compile directory?
>
> The problem: I have a many sub-folders in my project and when I edit a
> file deep inside subfolders and do M-x compile, I end up running make
> in that subfolder, instead of the root folder. Is there any way for
> Emacs to always run compile in the default folder?
>
> One thing I figured was to change default compile command to be: cd
> <project's root folder>; make. Is that the only/best way?

Hi Sumit,

You can use .dir-locals.el in your root folder and put something like:

(setq compile-command "cd <root folder>; make")

It will be evaluated every time you open a file in the folder. I think
it's a new feature of emacs 23.

Kind regards,
-- 
Ivan
Kanis http://kanis.fr

We know what we are, but know not what we may be.
    -- William Shakespeare 

Sumit Narayan <sumnaray@gmail.com> wrote:

Re: Default compile directory

[Peter Dyballa]

Am 17.08.2009 um 23:12 schrieb Sumit Narayan:

> One thing I figured was to change default compile command to be: cd
> <project's root folder>; make. Is that the only/best way?

No. You can also keep open a(n optionally minimised) second frame  
either with a buffer keeping open a file from your project's root  
directory, or a dired buffer from it, or the *compilation* buffer.  
When using GNU Emacs 23 you can in *compilation* buffer just type g  
(like update in dired) and the compilation process starts again.

--
Greetings

   Pete

If you're not confused, you're not paying attention.

Re: Default compile directory

[Sumit Narayan]

Thanks.

This is what I did:

Added
((nil . ((setq compile-command "cd <project root directory>; make"))))
in <project root directory>/.dir-locals.el.

When I open any file inside this folder, I am asked for permission to
apply the local variables

setq : (compile-command "cd <project root directory>; make")

For some reason, my response as 'y' or '!' does not make a difference.
When I give M-x compile, I still end up with "make -k".

Any idea why?

Thanks,
Sumit.


On Tue, Aug 18, 2009 at 1:38 AM, Ivan
Kanis<expire-by-2009-08-23@kanis.fr> wrote:
>
>> Is there any way to set default compile directory?
>>
>> The problem: I have a many sub-folders in my project and when I edit a
>> file deep inside subfolders and do M-x compile, I end up running make
>> in that subfolder, instead of the root folder. Is there any way for
>> Emacs to always run compile in the default folder?
>>
>> One thing I figured was to change default compile command to be: cd
>> <project's root folder>; make. Is that the only/best way?
>
> Hi Sumit,
>
> You can use .dir-locals.el in your root folder and put something like:
>
> (setq compile-command "cd <root folder>; make")
>
> It will be evaluated every time you open a file in the folder. I think
> it's a new feature of emacs 23.
>
> Kind regards,
> --
> Ivan
> Kanis http://kanis.fr
>
> We know what we are, but know not what we may be.
>    -- William Shakespeare
>
> Sumit Narayan <sumnaray@gmail.com> wrote:
>

Re: Default compile directory

[Sumit Narayan]

Thanks Peter. This is a nice feature. I wasn't aware of it and I think
it is quite useful.

However, I have my compilation window close on its own if there were
no errors. To recompile, I will have to change to that buffer, which I
do not wish to. Emacs anyway saves the previous compile command. I
only need to give the compile command once in the project folder. But
if I move to another project, I will have to give the compile command
again. .dir-locals.el seems like something I could use.

Sumit.



On Tue, Aug 18, 2009 at 4:15 AM, Peter Dyballa<Peter_Dyballa@web.de> wrote:
>
> Am 17.08.2009 um 23:12 schrieb Sumit Narayan:
>
>> One thing I figured was to change default compile command to be: cd
>> <project's root folder>; make. Is that the only/best way?
>
> No. You can also keep open a(n optionally minimised) second frame either
> with a buffer keeping open a file from your project's root directory, or a
> dired buffer from it, or the *compilation* buffer. When using GNU Emacs 23
> you can in *compilation* buffer just type g (like update in dired) and the
> compilation process starts again.
>
> --
> Greetings
>
>  Pete
>
> If you're not confused, you're not paying attention.
>
>
>
>

Re: Default compile directory

[Nikolaj Schumacher]

Sumit Narayan <sumnaray@gmail.com> wrote:

> The problem: I have a many sub-folders in my project and when I edit a
> file deep inside subfolders and do M-x compile, I end up running make
> in that subfolder, instead of the root folder. Is there any way for
> Emacs to always run compile in the default folder?

In most cases you'll want to use M-x recompile to avoid this.

regards,
Nikolaj Schumacher

Re: Default compile directory

[A.Politz]

On Aug 18, 9:59 pm, Sumit Narayan <sumna...@gmail.com> wrote:

>
> This is what I did:
>
> Added
> ((nil . ((setq compile-command "cd <project root directory>; make"))))
> in <project root directory>/.dir-locals.el.
>
> [does not work]

According to the info doc, the syntax is similar to a let-list.
So, delete the 'setq' and it should work.



-ap

Re: Default compile directory

[Sumit Narayan]

Thanks Politz. I was also missing a dot.

For those who might be looking at this in future, this is how I got it
working. Add

((nil . ((compile-command . "cd <project root directory>; make"))))

in <project root directory>/.dir-locals.el.

Sumit.



On Fri, Aug 21, 2009 at 10:32 AM, A.Politz<politza@googlemail.com> wrote:
> On Aug 18, 9:59 pm, Sumit Narayan <sumna...@gmail.com> wrote:
>
>>
>> This is what I did:
>>
>> Added
>> ((nil . ((setq compile-command "cd <project root directory>; make"))))
>> in <project root directory>/.dir-locals.el.
>>
>> [does not work]
>
> According to the info doc, the syntax is similar to a let-list.
> So, delete the 'setq' and it should work.
>
>
>
> -ap
>

Re: Default compile directory

[Sumit Narayan]

Back to this topic.

This only works if I my frame has some code open. But if I am in an
eshell frame, it goes back to the default compile command - 'make -k'.
Is that how it is supposed to be?

Thanks,
Sumit.



On Fri, Aug 21, 2009 at 11:23 AM, Sumit Narayan<sumnaray@gmail.com> wrote:
> Thanks Politz. I was also missing a dot.
>
> For those who might be looking at this in future, this is how I got it
> working. Add
>
> ((nil . ((compile-command . "cd <project root directory>; make"))))
>
> in <project root directory>/.dir-locals.el.
>
> Sumit.
>
>
>
> On Fri, Aug 21, 2009 at 10:32 AM, A.Politz<politza@googlemail.com> wrote:
>> On Aug 18, 9:59 pm, Sumit Narayan <sumna...@gmail.com> wrote:
>>
>>>
>>> This is what I did:
>>>
>>> Added
>>> ((nil . ((setq compile-command "cd <project root directory>; make"))))
>>> in <project root directory>/.dir-locals.el.
>>>
>>> [does not work]
>>
>> According to the info doc, the syntax is similar to a let-list.
>> So, delete the 'setq' and it should work.
>>
>>
>>
>> -ap
>>
>