(require) is still required, even after (package-initialize)

(require) is still required, even after (package-initialize)

[Pankaj Jangid]

The documentation says that (require 'package) is not required if
(package-initialize) is already invoked in init.el.

But flymake is reporting "server-running-p is not known to be defined"
in the below statement,

(unless (server-running-p) (server-start))

I have also tried to call,

(eval-when-compile (package-initialize)) instead of just
(package-initialize). But still flymake is reporting the error.

(require 'server) solves the error.

Am I using package-initialize wrongly?

-- 
Pankaj Jangid

Re: (require) is still required, even after (package-initialize)

[Michael Heerdegen]

Pankaj Jangid <pankaj.jangid@gmail.com> writes:

> The documentation says that (require 'package) is not required if
> (package-initialize) is already invoked in init.el.
>
> But flymake is reporting "server-running-p is not known to be defined"
> in the below statement,
>
> (unless (server-running-p) (server-start))
>
> I have also tried to call,
>
> (eval-when-compile (package-initialize)) instead of just
> (package-initialize). But still flymake is reporting the error.
>
> (require 'server) solves the error.
>
> Am I using package-initialize wrongly?

No, probably not.  "server" is built-in Emacs, so (package-initialize)
will not help.  Maybe it's a bug in a flymake addon package you use?  I
don't the the flymake source files in Emacs doing anything with the
server.  What's your setup - or do you have a recipe?

Regards,

Michael.

Re: (require) is still required, even after (package-initialize)

[Pankaj Jangid]

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Pankaj Jangid <pankaj.jangid@gmail.com> writes:
>
>> The documentation says that (require 'package) is not required if
>> (package-initialize) is already invoked in init.el.
>>
>> But flymake is reporting "server-running-p is not known to be defined"
>> in the below statement,
>>
>> (unless (server-running-p) (server-start))
>>
>> I have also tried to call,
>>
>> (eval-when-compile (package-initialize)) instead of just
>> (package-initialize). But still flymake is reporting the error.
>>
>> (require 'server) solves the error.
>>
>> Am I using package-initialize wrongly?
>
> No, probably not.  "server" is built-in Emacs, so (package-initialize)
> will not help.  Maybe it's a bug in a flymake addon package you use?  I
> don't the the flymake source files in Emacs doing anything with the
> server.  What's your setup - or do you have a recipe?
>

I am using the built-in flymake only. Have installed only two
extensions:

flymake-rust
flymake-lua

But I don't think this is causing any issue in init.el. For server
setup, I have only this in my init.el:

;; start server for emacsclient support
(require 'server)			; I don't know why this is
					; required after
					; package-initialize
(unless (server-running-p) (server-start))


Regards,
-- 
Pankaj Jangid

Re: (require) is still required, even after (package-initialize)

[Michael Heerdegen]

Pankaj Jangid <pankaj.jangid@gmail.com> writes:

> But I don't think this is causing any issue in init.el. For server
> setup, I have only this in my init.el:
>
> ;; start server for emacsclient support
> (require 'server)			; I don't know why this is
> 					; required after
> 					; package-initialize
> (unless (server-running-p) (server-start))

Ok, so there is no relation to flymake.

"server" is a built-in library, and `server-running-p' is not an
autoload function, so (require 'server) is needed in your init file.

package.el is the Emacs package manager to install packages from outside
repositories.  `package-intitialize' activates your installed packages
(it doesn't load them).  But that doesn't matter here since server is
not a package at all.  You want to keep `package-intitialize' and you
use it correctly, it just doesn't cover as much as you thought.

Did that answer all of your questions?


Regards,

Michael.