From: Narendra Joshi <narendraj9@gmail.com>
To: Alex Kost <alezost@gmail.com>
Cc: Gnu Emacs Help <help-gnu-emacs@gnu.org>
Subject: Re: A package for common configuration options with use-package
Date: Sat, 11 Mar 2017 01:57:32 +0530 [thread overview]
Message-ID: <87d1do98sr.fsf@vicarie> (raw)
In-Reply-To: <87h9327flw.fsf@gmail.com> (Alex Kost's message of "Thu, 09 Mar 2017 16:18:51 +0300")
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
prev parent reply other threads:[~2017-03-10 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 16:55 A package for common configuration options with use-package Narendra Joshi
2017-03-07 17:00 ` Kaushal Modi
2017-03-07 18:47 ` Narendra Joshi
2017-03-07 18:45 ` Kaushal Modi
2017-03-07 19:37 ` Narendra Joshi
2017-03-07 17:47 ` Alex Kost
2017-03-07 19:38 ` Narendra Joshi
2017-03-09 13:18 ` Alex Kost
2017-03-10 20:27 ` Narendra Joshi [this message]
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=87d1do98sr.fsf@vicarie \
--to=narendraj9@gmail.com \
--cc=alezost@gmail.com \
--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).