Managing libraries hosted on EmacsWikiHow can I improve startup time despite many packages?

What is the "ls" directory in my home directory?

Tznius concerns by a Sota

"What is the maximum that Player 1 can win?"

How did Frodo know where the Bree village was?

If the mass of the Earth is decreasing by sending debris in space, does its angular momentum also decrease?

Predict the product from the reaction

Are there examples of rowers who also fought?

Why is it 出差去 and not 去出差?

Scaling an object to change its key

What is the highest power supply a Raspberry pi 3 B can handle without getting damaged?

「捨ててしまう」why is there two て’s used here?

Why isn't my calculation that we should be able to see the sun well beyond the observable universe valid?

A conjecture concerning symmetric convex sets

Elementary, my dear …

Synaptic Static - when to roll the d6?

Explicit song lyrics checker

Unrecognized IC Package Style

How can a clan of females defend themselves in the ancient world against wandering bands?

Implementation of the Jacobi Symbol in C

Story of a Witch Boy

Explain why a line can never intersect a plane in exactly two points.

Time at 1 g acceleration to travel 100 000 light years

Is there a term for the belief that "if it's legal, it's moral"?

What preparations would Hubble have needed to return in a Shuttle?



Managing libraries hosted on EmacsWiki


How can I improve startup time despite many packages?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2















I recently learned that some former MELPA libraries are now available only from the EmacsWiki.



Let aside security implications,



Is there an equivalent of M-x package-list-packages for those libraries?

Is there an equivalent of (use-package foo), which I could put in my init file?

Any best practice suggested to deal with EmacsWiki libraries?










share|improve this question






























    2















    I recently learned that some former MELPA libraries are now available only from the EmacsWiki.



    Let aside security implications,



    Is there an equivalent of M-x package-list-packages for those libraries?

    Is there an equivalent of (use-package foo), which I could put in my init file?

    Any best practice suggested to deal with EmacsWiki libraries?










    share|improve this question


























      2












      2








      2








      I recently learned that some former MELPA libraries are now available only from the EmacsWiki.



      Let aside security implications,



      Is there an equivalent of M-x package-list-packages for those libraries?

      Is there an equivalent of (use-package foo), which I could put in my init file?

      Any best practice suggested to deal with EmacsWiki libraries?










      share|improve this question
















      I recently learned that some former MELPA libraries are now available only from the EmacsWiki.



      Let aside security implications,



      Is there an equivalent of M-x package-list-packages for those libraries?

      Is there an equivalent of (use-package foo), which I could put in my init file?

      Any best practice suggested to deal with EmacsWiki libraries?







      package emacs-wiki






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 2 at 2:19









      Drew

      49.7k465112




      49.7k465112










      asked Jun 2 at 1:44









      antonioantonio

      876512




      876512




















          2 Answers
          2






          active

          oldest

          votes


















          5















          Is there an equivalent of M-x package-list-packages for those libraries?




          The el-get package manager supports installation from the EmacsWiki; after doing M-x el-get-emacswiki-build-local-recipes, M-x el-get-list-packages will show packages from EmacsWiki as well.




          Is there an equivalent of (use-package foo), which I could put in my init file?




          (el-get-bundle foo) would be approximately equivalent.






          share|improve this answer























          • +1. Good to know. I didn't realize that el-get works with Emacs-Wiki libraries also.

            – Drew
            Jun 2 at 14:22











          • I tried to add to my init (use-package el-get :config (el-get-emacswiki-build-local-recipes)) (el-get-bundle dired+). However, el-get-bundle raises an error, when generating autoloads and byte-compiling the autoload file, because dired-omit-files is void. A hack would be to (setq dired-omit-files nil), but clearly there should be a proper way.

            – antonio
            Jun 3 at 7:55











          • @antonio oh, you have to load el-get before using el-get-bundle (because it's a macro), you can't start using it in the same statement that you load it. Maybe try (el-get nil 'dired+) instead. And el-get-emacswiki-build-local-recipes takes a long time, you probably don't want to run it every time you startup.

            – npostavs
            Jun 3 at 11:47











          • As regards (el-get-emacswiki-build-local-recipes), use-package :config is clever enough to run it only the first time. Still (el-get nil 'dired+) gives error in process sentinel: Symbol’s value as variable is void: dired-omit-files. The mentioned variable is part part of dired (not dired+), which is not loaded by el-get. Byte-compiling dired+ works, so the problem is in the way el-get installs dired+.

            – antonio
            Jun 3 at 14:03











          • @antonio oh, I misread the error in your first comment. I think it's due to dired+ misusing ;;;###autoload. You can work around it with (add-to-list 'el-get-sources '(:name dired+ :autoloads nil)) before the (el-get nil 'dired+) call, or using el-get-bundle: (el-get-bundle dired+ :autoloads nil).

            – npostavs
            Jun 3 at 20:48


















          1














          1. No. As far as I know, there is no equivalent of package-list-packages or use-package for libraries uploaded to the Emacs Wiki Elisp Area. In general, you download the file(s) for a library to a local directory that is in your load-path, and then require the library feature name or main-file name (e.g. (require 'isearch+).


          2. Questions about things such as best practice are off-topic on emacs.SE, as they are generally primarily opinion-based or too broad. Questions here should be specific and call for specific answers.


          3. Anyone can upload code to Emacs Wiki. As a result, the code there is variable in what it does, how it does it, and perhaps how well it does it. As is true in general elsewhere, it's a good idea to take a look at code you download before using it, and preferably take a look at any associated doc there may be for it.






          share|improve this answer























          • Please consider moving your comment to @npostavs's answer about elget. My answer only speaks about downloading libraries to a local directory that you add to your load-path, and then require-ing those libraries. Doing that, I think you will encounter no such problem.

            – Drew
            Jun 3 at 3:40











          • Hey, @Drew, as you are the author of by far the largest number of useful libraries on EmacsWiki (thank you!), can you explain why you choose that as your publishing mechanism?

            – Phil Hudson
            Jun 4 at 23:14











          • @PhilHudson: Laziness. See reddit.com/r/emacs/comments/7vocqa/….

            – Drew
            Jun 4 at 23:20











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "583"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2femacs.stackexchange.com%2fquestions%2f50815%2fmanaging-libraries-hosted-on-emacswiki%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          5















          Is there an equivalent of M-x package-list-packages for those libraries?




          The el-get package manager supports installation from the EmacsWiki; after doing M-x el-get-emacswiki-build-local-recipes, M-x el-get-list-packages will show packages from EmacsWiki as well.




          Is there an equivalent of (use-package foo), which I could put in my init file?




          (el-get-bundle foo) would be approximately equivalent.






          share|improve this answer























          • +1. Good to know. I didn't realize that el-get works with Emacs-Wiki libraries also.

            – Drew
            Jun 2 at 14:22











          • I tried to add to my init (use-package el-get :config (el-get-emacswiki-build-local-recipes)) (el-get-bundle dired+). However, el-get-bundle raises an error, when generating autoloads and byte-compiling the autoload file, because dired-omit-files is void. A hack would be to (setq dired-omit-files nil), but clearly there should be a proper way.

            – antonio
            Jun 3 at 7:55











          • @antonio oh, you have to load el-get before using el-get-bundle (because it's a macro), you can't start using it in the same statement that you load it. Maybe try (el-get nil 'dired+) instead. And el-get-emacswiki-build-local-recipes takes a long time, you probably don't want to run it every time you startup.

            – npostavs
            Jun 3 at 11:47











          • As regards (el-get-emacswiki-build-local-recipes), use-package :config is clever enough to run it only the first time. Still (el-get nil 'dired+) gives error in process sentinel: Symbol’s value as variable is void: dired-omit-files. The mentioned variable is part part of dired (not dired+), which is not loaded by el-get. Byte-compiling dired+ works, so the problem is in the way el-get installs dired+.

            – antonio
            Jun 3 at 14:03











          • @antonio oh, I misread the error in your first comment. I think it's due to dired+ misusing ;;;###autoload. You can work around it with (add-to-list 'el-get-sources '(:name dired+ :autoloads nil)) before the (el-get nil 'dired+) call, or using el-get-bundle: (el-get-bundle dired+ :autoloads nil).

            – npostavs
            Jun 3 at 20:48















          5















          Is there an equivalent of M-x package-list-packages for those libraries?




          The el-get package manager supports installation from the EmacsWiki; after doing M-x el-get-emacswiki-build-local-recipes, M-x el-get-list-packages will show packages from EmacsWiki as well.




          Is there an equivalent of (use-package foo), which I could put in my init file?




          (el-get-bundle foo) would be approximately equivalent.






          share|improve this answer























          • +1. Good to know. I didn't realize that el-get works with Emacs-Wiki libraries also.

            – Drew
            Jun 2 at 14:22











          • I tried to add to my init (use-package el-get :config (el-get-emacswiki-build-local-recipes)) (el-get-bundle dired+). However, el-get-bundle raises an error, when generating autoloads and byte-compiling the autoload file, because dired-omit-files is void. A hack would be to (setq dired-omit-files nil), but clearly there should be a proper way.

            – antonio
            Jun 3 at 7:55











          • @antonio oh, you have to load el-get before using el-get-bundle (because it's a macro), you can't start using it in the same statement that you load it. Maybe try (el-get nil 'dired+) instead. And el-get-emacswiki-build-local-recipes takes a long time, you probably don't want to run it every time you startup.

            – npostavs
            Jun 3 at 11:47











          • As regards (el-get-emacswiki-build-local-recipes), use-package :config is clever enough to run it only the first time. Still (el-get nil 'dired+) gives error in process sentinel: Symbol’s value as variable is void: dired-omit-files. The mentioned variable is part part of dired (not dired+), which is not loaded by el-get. Byte-compiling dired+ works, so the problem is in the way el-get installs dired+.

            – antonio
            Jun 3 at 14:03











          • @antonio oh, I misread the error in your first comment. I think it's due to dired+ misusing ;;;###autoload. You can work around it with (add-to-list 'el-get-sources '(:name dired+ :autoloads nil)) before the (el-get nil 'dired+) call, or using el-get-bundle: (el-get-bundle dired+ :autoloads nil).

            – npostavs
            Jun 3 at 20:48













          5












          5








          5








          Is there an equivalent of M-x package-list-packages for those libraries?




          The el-get package manager supports installation from the EmacsWiki; after doing M-x el-get-emacswiki-build-local-recipes, M-x el-get-list-packages will show packages from EmacsWiki as well.




          Is there an equivalent of (use-package foo), which I could put in my init file?




          (el-get-bundle foo) would be approximately equivalent.






          share|improve this answer














          Is there an equivalent of M-x package-list-packages for those libraries?




          The el-get package manager supports installation from the EmacsWiki; after doing M-x el-get-emacswiki-build-local-recipes, M-x el-get-list-packages will show packages from EmacsWiki as well.




          Is there an equivalent of (use-package foo), which I could put in my init file?




          (el-get-bundle foo) would be approximately equivalent.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jun 2 at 12:10









          npostavsnpostavs

          7,20611237




          7,20611237












          • +1. Good to know. I didn't realize that el-get works with Emacs-Wiki libraries also.

            – Drew
            Jun 2 at 14:22











          • I tried to add to my init (use-package el-get :config (el-get-emacswiki-build-local-recipes)) (el-get-bundle dired+). However, el-get-bundle raises an error, when generating autoloads and byte-compiling the autoload file, because dired-omit-files is void. A hack would be to (setq dired-omit-files nil), but clearly there should be a proper way.

            – antonio
            Jun 3 at 7:55











          • @antonio oh, you have to load el-get before using el-get-bundle (because it's a macro), you can't start using it in the same statement that you load it. Maybe try (el-get nil 'dired+) instead. And el-get-emacswiki-build-local-recipes takes a long time, you probably don't want to run it every time you startup.

            – npostavs
            Jun 3 at 11:47











          • As regards (el-get-emacswiki-build-local-recipes), use-package :config is clever enough to run it only the first time. Still (el-get nil 'dired+) gives error in process sentinel: Symbol’s value as variable is void: dired-omit-files. The mentioned variable is part part of dired (not dired+), which is not loaded by el-get. Byte-compiling dired+ works, so the problem is in the way el-get installs dired+.

            – antonio
            Jun 3 at 14:03











          • @antonio oh, I misread the error in your first comment. I think it's due to dired+ misusing ;;;###autoload. You can work around it with (add-to-list 'el-get-sources '(:name dired+ :autoloads nil)) before the (el-get nil 'dired+) call, or using el-get-bundle: (el-get-bundle dired+ :autoloads nil).

            – npostavs
            Jun 3 at 20:48

















          • +1. Good to know. I didn't realize that el-get works with Emacs-Wiki libraries also.

            – Drew
            Jun 2 at 14:22











          • I tried to add to my init (use-package el-get :config (el-get-emacswiki-build-local-recipes)) (el-get-bundle dired+). However, el-get-bundle raises an error, when generating autoloads and byte-compiling the autoload file, because dired-omit-files is void. A hack would be to (setq dired-omit-files nil), but clearly there should be a proper way.

            – antonio
            Jun 3 at 7:55











          • @antonio oh, you have to load el-get before using el-get-bundle (because it's a macro), you can't start using it in the same statement that you load it. Maybe try (el-get nil 'dired+) instead. And el-get-emacswiki-build-local-recipes takes a long time, you probably don't want to run it every time you startup.

            – npostavs
            Jun 3 at 11:47











          • As regards (el-get-emacswiki-build-local-recipes), use-package :config is clever enough to run it only the first time. Still (el-get nil 'dired+) gives error in process sentinel: Symbol’s value as variable is void: dired-omit-files. The mentioned variable is part part of dired (not dired+), which is not loaded by el-get. Byte-compiling dired+ works, so the problem is in the way el-get installs dired+.

            – antonio
            Jun 3 at 14:03











          • @antonio oh, I misread the error in your first comment. I think it's due to dired+ misusing ;;;###autoload. You can work around it with (add-to-list 'el-get-sources '(:name dired+ :autoloads nil)) before the (el-get nil 'dired+) call, or using el-get-bundle: (el-get-bundle dired+ :autoloads nil).

            – npostavs
            Jun 3 at 20:48
















          +1. Good to know. I didn't realize that el-get works with Emacs-Wiki libraries also.

          – Drew
          Jun 2 at 14:22





          +1. Good to know. I didn't realize that el-get works with Emacs-Wiki libraries also.

          – Drew
          Jun 2 at 14:22













          I tried to add to my init (use-package el-get :config (el-get-emacswiki-build-local-recipes)) (el-get-bundle dired+). However, el-get-bundle raises an error, when generating autoloads and byte-compiling the autoload file, because dired-omit-files is void. A hack would be to (setq dired-omit-files nil), but clearly there should be a proper way.

          – antonio
          Jun 3 at 7:55





          I tried to add to my init (use-package el-get :config (el-get-emacswiki-build-local-recipes)) (el-get-bundle dired+). However, el-get-bundle raises an error, when generating autoloads and byte-compiling the autoload file, because dired-omit-files is void. A hack would be to (setq dired-omit-files nil), but clearly there should be a proper way.

          – antonio
          Jun 3 at 7:55













          @antonio oh, you have to load el-get before using el-get-bundle (because it's a macro), you can't start using it in the same statement that you load it. Maybe try (el-get nil 'dired+) instead. And el-get-emacswiki-build-local-recipes takes a long time, you probably don't want to run it every time you startup.

          – npostavs
          Jun 3 at 11:47





          @antonio oh, you have to load el-get before using el-get-bundle (because it's a macro), you can't start using it in the same statement that you load it. Maybe try (el-get nil 'dired+) instead. And el-get-emacswiki-build-local-recipes takes a long time, you probably don't want to run it every time you startup.

          – npostavs
          Jun 3 at 11:47













          As regards (el-get-emacswiki-build-local-recipes), use-package :config is clever enough to run it only the first time. Still (el-get nil 'dired+) gives error in process sentinel: Symbol’s value as variable is void: dired-omit-files. The mentioned variable is part part of dired (not dired+), which is not loaded by el-get. Byte-compiling dired+ works, so the problem is in the way el-get installs dired+.

          – antonio
          Jun 3 at 14:03





          As regards (el-get-emacswiki-build-local-recipes), use-package :config is clever enough to run it only the first time. Still (el-get nil 'dired+) gives error in process sentinel: Symbol’s value as variable is void: dired-omit-files. The mentioned variable is part part of dired (not dired+), which is not loaded by el-get. Byte-compiling dired+ works, so the problem is in the way el-get installs dired+.

          – antonio
          Jun 3 at 14:03













          @antonio oh, I misread the error in your first comment. I think it's due to dired+ misusing ;;;###autoload. You can work around it with (add-to-list 'el-get-sources '(:name dired+ :autoloads nil)) before the (el-get nil 'dired+) call, or using el-get-bundle: (el-get-bundle dired+ :autoloads nil).

          – npostavs
          Jun 3 at 20:48





          @antonio oh, I misread the error in your first comment. I think it's due to dired+ misusing ;;;###autoload. You can work around it with (add-to-list 'el-get-sources '(:name dired+ :autoloads nil)) before the (el-get nil 'dired+) call, or using el-get-bundle: (el-get-bundle dired+ :autoloads nil).

          – npostavs
          Jun 3 at 20:48













          1














          1. No. As far as I know, there is no equivalent of package-list-packages or use-package for libraries uploaded to the Emacs Wiki Elisp Area. In general, you download the file(s) for a library to a local directory that is in your load-path, and then require the library feature name or main-file name (e.g. (require 'isearch+).


          2. Questions about things such as best practice are off-topic on emacs.SE, as they are generally primarily opinion-based or too broad. Questions here should be specific and call for specific answers.


          3. Anyone can upload code to Emacs Wiki. As a result, the code there is variable in what it does, how it does it, and perhaps how well it does it. As is true in general elsewhere, it's a good idea to take a look at code you download before using it, and preferably take a look at any associated doc there may be for it.






          share|improve this answer























          • Please consider moving your comment to @npostavs's answer about elget. My answer only speaks about downloading libraries to a local directory that you add to your load-path, and then require-ing those libraries. Doing that, I think you will encounter no such problem.

            – Drew
            Jun 3 at 3:40











          • Hey, @Drew, as you are the author of by far the largest number of useful libraries on EmacsWiki (thank you!), can you explain why you choose that as your publishing mechanism?

            – Phil Hudson
            Jun 4 at 23:14











          • @PhilHudson: Laziness. See reddit.com/r/emacs/comments/7vocqa/….

            – Drew
            Jun 4 at 23:20















          1














          1. No. As far as I know, there is no equivalent of package-list-packages or use-package for libraries uploaded to the Emacs Wiki Elisp Area. In general, you download the file(s) for a library to a local directory that is in your load-path, and then require the library feature name or main-file name (e.g. (require 'isearch+).


          2. Questions about things such as best practice are off-topic on emacs.SE, as they are generally primarily opinion-based or too broad. Questions here should be specific and call for specific answers.


          3. Anyone can upload code to Emacs Wiki. As a result, the code there is variable in what it does, how it does it, and perhaps how well it does it. As is true in general elsewhere, it's a good idea to take a look at code you download before using it, and preferably take a look at any associated doc there may be for it.






          share|improve this answer























          • Please consider moving your comment to @npostavs's answer about elget. My answer only speaks about downloading libraries to a local directory that you add to your load-path, and then require-ing those libraries. Doing that, I think you will encounter no such problem.

            – Drew
            Jun 3 at 3:40











          • Hey, @Drew, as you are the author of by far the largest number of useful libraries on EmacsWiki (thank you!), can you explain why you choose that as your publishing mechanism?

            – Phil Hudson
            Jun 4 at 23:14











          • @PhilHudson: Laziness. See reddit.com/r/emacs/comments/7vocqa/….

            – Drew
            Jun 4 at 23:20













          1












          1








          1







          1. No. As far as I know, there is no equivalent of package-list-packages or use-package for libraries uploaded to the Emacs Wiki Elisp Area. In general, you download the file(s) for a library to a local directory that is in your load-path, and then require the library feature name or main-file name (e.g. (require 'isearch+).


          2. Questions about things such as best practice are off-topic on emacs.SE, as they are generally primarily opinion-based or too broad. Questions here should be specific and call for specific answers.


          3. Anyone can upload code to Emacs Wiki. As a result, the code there is variable in what it does, how it does it, and perhaps how well it does it. As is true in general elsewhere, it's a good idea to take a look at code you download before using it, and preferably take a look at any associated doc there may be for it.






          share|improve this answer













          1. No. As far as I know, there is no equivalent of package-list-packages or use-package for libraries uploaded to the Emacs Wiki Elisp Area. In general, you download the file(s) for a library to a local directory that is in your load-path, and then require the library feature name or main-file name (e.g. (require 'isearch+).


          2. Questions about things such as best practice are off-topic on emacs.SE, as they are generally primarily opinion-based or too broad. Questions here should be specific and call for specific answers.


          3. Anyone can upload code to Emacs Wiki. As a result, the code there is variable in what it does, how it does it, and perhaps how well it does it. As is true in general elsewhere, it's a good idea to take a look at code you download before using it, and preferably take a look at any associated doc there may be for it.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jun 2 at 2:17









          DrewDrew

          49.7k465112




          49.7k465112












          • Please consider moving your comment to @npostavs's answer about elget. My answer only speaks about downloading libraries to a local directory that you add to your load-path, and then require-ing those libraries. Doing that, I think you will encounter no such problem.

            – Drew
            Jun 3 at 3:40











          • Hey, @Drew, as you are the author of by far the largest number of useful libraries on EmacsWiki (thank you!), can you explain why you choose that as your publishing mechanism?

            – Phil Hudson
            Jun 4 at 23:14











          • @PhilHudson: Laziness. See reddit.com/r/emacs/comments/7vocqa/….

            – Drew
            Jun 4 at 23:20

















          • Please consider moving your comment to @npostavs's answer about elget. My answer only speaks about downloading libraries to a local directory that you add to your load-path, and then require-ing those libraries. Doing that, I think you will encounter no such problem.

            – Drew
            Jun 3 at 3:40











          • Hey, @Drew, as you are the author of by far the largest number of useful libraries on EmacsWiki (thank you!), can you explain why you choose that as your publishing mechanism?

            – Phil Hudson
            Jun 4 at 23:14











          • @PhilHudson: Laziness. See reddit.com/r/emacs/comments/7vocqa/….

            – Drew
            Jun 4 at 23:20
















          Please consider moving your comment to @npostavs's answer about elget. My answer only speaks about downloading libraries to a local directory that you add to your load-path, and then require-ing those libraries. Doing that, I think you will encounter no such problem.

          – Drew
          Jun 3 at 3:40





          Please consider moving your comment to @npostavs's answer about elget. My answer only speaks about downloading libraries to a local directory that you add to your load-path, and then require-ing those libraries. Doing that, I think you will encounter no such problem.

          – Drew
          Jun 3 at 3:40













          Hey, @Drew, as you are the author of by far the largest number of useful libraries on EmacsWiki (thank you!), can you explain why you choose that as your publishing mechanism?

          – Phil Hudson
          Jun 4 at 23:14





          Hey, @Drew, as you are the author of by far the largest number of useful libraries on EmacsWiki (thank you!), can you explain why you choose that as your publishing mechanism?

          – Phil Hudson
          Jun 4 at 23:14













          @PhilHudson: Laziness. See reddit.com/r/emacs/comments/7vocqa/….

          – Drew
          Jun 4 at 23:20





          @PhilHudson: Laziness. See reddit.com/r/emacs/comments/7vocqa/….

          – Drew
          Jun 4 at 23:20

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Emacs Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2femacs.stackexchange.com%2fquestions%2f50815%2fmanaging-libraries-hosted-on-emacswiki%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

          Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

          What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company