A package for common configuration options with use-package

A package for common configuration options with use-package

[Narendra Joshi]

Hi,

I have started organizing my Emacs configuration with `use-package'. I
like to keep everything inside some or the other `use-package'
declaration. How do you deal with configuration that is in an Elisp file
that doesn't `provide` any symbol. 

Thanks,
-- 
Narendra Joshi

Re: A package for common configuration options with use-package

[Kaushal Modi]

On Tue, Mar 7, 2017 at 11:51 AM Narendra Joshi <narendraj9@gmail.com> wrote:

> Hi,
>
> I have started organizing my Emacs configuration with `use-package'. I
> like to keep everything inside some or the other `use-package'
> declaration.




> How do you deal with configuration that is in an Elisp file
> that doesn't `provide` any symbol.


What would be such examples?
-- 

Kaushal Modi

Re: A package for common configuration options with use-package

[Alex Kost]

Narendra Joshi (2017-03-07 22:25 +0530) wrote:

> Hi,
>
> I have started organizing my Emacs configuration with `use-package'. I
> like to keep everything inside some or the other `use-package'
> declaration. How do you deal with configuration that is in an Elisp file
> that doesn't `provide` any symbol.

IIRC, you can use (use-package "foo" ...), where "foo.el" is the file
that does not provide a feature.

-- 
Alex

Re: A package for common configuration options with use-package

[Kaushal Modi]

On Tue, Mar 7, 2017 at 1:42 PM Narendra Joshi <narendraj9@gmail.com> wrote:

> > What would be such examples?
> The variable `inhibit-splash-screen' from `startup.el'.
>

I am wondering how using use-package will benefit there..

You can simply put

(setq inhibit-startup-message t)

or even

(progn
  ;; more such setq
  (setq inhibit-startup-message t))

to group things together.
-- 

Kaushal Modi

Re: A package for common configuration options with use-package

[Narendra Joshi]

Kaushal Modi <kaushal.modi@gmail.com> writes:

> On Tue, Mar 7, 2017 at 11:51 AM Narendra Joshi <narendraj9@gmail.com>
> wrote:
>
>     Hi,
>    
>     I have started organizing my Emacs configuration with
>     `use-package'. I
>     like to keep everything inside some or the other `use-package'
>     declaration.
>
>
>  
>
>     How do you deal with configuration that is in an Elisp file
>     that doesn't `provide` any symbol.
>
>
> What would be such examples? 
The variable `inhibit-splash-screen' from `startup.el'. 

>

-- 
Narendra Joshi

Re: A package for common configuration options with use-package

[Narendra Joshi]

Kaushal Modi <kaushal.modi@gmail.com> writes:

> On Tue, Mar 7, 2017 at 1:42 PM Narendra Joshi <narendraj9@gmail.com>
> wrote:
>
>     > What would be such examples? 
>     The variable `inhibit-splash-screen' from `startup.el'.
>
>
> I am wondering how using use-package will benefit there..
I just happen to like doing it. No benefit, no loss.
I usually do:

(use-package feature
    :doc "Something about the config"
    ...)

> You can simply put
>
> (setq inhibit-startup-message t)
>
> or even
>
> (progn
>   ;; more such setq 
>   (setq inhibit-startup-message t)) 
> to group things together.
Yes, this can be done. Thanks.

> --
>
> Kaushal Modi
>
>
>

-- 
Narendra Joshi

Re: A package for common configuration options with use-package

[Narendra Joshi]

Alex Kost <alezost@gmail.com> writes:

> Narendra Joshi (2017-03-07 22:25 +0530) wrote:
>
>> Hi,
>>
>> I have started organizing my Emacs configuration with `use-package'. I
>> like to keep everything inside some or the other `use-package'
>> declaration. How do you deal with configuration that is in an Elisp file
>> that doesn't `provide` any symbol.
>
> IIRC, you can use (use-package "foo" ...), where "foo.el" is the file
> that does not provide a feature.

Sadly
(use-package startup
  ...)
didn't work for me.

The only way I think I can do this is to create empty Elisp files that
provide some feature.

-- 
Narendra Joshi

Re: A package for common configuration options with use-package

[Alex Kost]

Narendra Joshi (2017-03-08 01:08 +0530) wrote:

> Alex Kost <alezost@gmail.com> writes:
>
>> Narendra Joshi (2017-03-07 22:25 +0530) wrote:
>>
>>> Hi,
>>>
>>> I have started organizing my Emacs configuration with `use-package'. I
>>> like to keep everything inside some or the other `use-package'
>>> declaration. How do you deal with configuration that is in an Elisp file
>>> that doesn't `provide` any symbol.
>>
>> IIRC, you can use (use-package "foo" ...), where "foo.el" is the file
>> that does not provide a feature.
>
> Sadly
> (use-package startup
>   ...)
> didn't work for me.

I told about (use-package "foo" ...) not (use-package foo ...).  Did you
try (use-package "startup" ...)?

> The only way I think I can do this is to create empty Elisp files that
> provide some feature.

This looks like a redundant complication for me.  I agree with Kaushal,
that you can simply use:

  (setq inhibit-startup-message t)

without touching use-package at all.

-- 
Alex

Re: A package for common configuration options with use-package

[Narendra Joshi]

Alex Kost <alezost@gmail.com> writes:

> Narendra Joshi (2017-03-08 01:08 +0530) wrote:
>
>> Alex Kost <alezost@gmail.com> writes:
>>
>>> Narendra Joshi (2017-03-07 22:25 +0530) wrote:
>>>
>>>> Hi,
>>>>
>>>> I have started organizing my Emacs configuration with `use-package'. I
>>>> like to keep everything inside some or the other `use-package'
>>>> declaration. How do you deal with configuration that is in an Elisp file
>>>> that doesn't `provide` any symbol.
>>>
>>> IIRC, you can use (use-package "foo" ...), where "foo.el" is the file
>>> that does not provide a feature.
>>
>> Sadly
>> (use-package startup
>>   ...)
>> didn't work for me.
>
> I told about (use-package "foo" ...) not (use-package foo ...).  Did you
> try (use-package "startup" ...)?
No, I hadn't tried (use-package "foo"). I will try it thanks. :)

>> The only way I think I can do this is to create empty Elisp files that
>> provide some feature.
>
> This looks like a redundant complication for me.  I agree with Kaushal,
> that you can simply use:
>
>   (setq inhibit-startup-message t)
>
> without touching use-package at all.
Now, that I have moved most of my configuration into `use-package'
declarations, I agree with you and Kaushal to some extent.

-- 
Narendra Joshi