novoid / Memacs

What did I do on February 14th 2007? Visualize your (digital) life in Org-mode
GNU General Public License v3.0
1.03k stars 66 forks source link

Don't depend on PIL #15

Closed Wilfred closed 10 years ago

Wilfred commented 10 years ago

Trying to install memacs gives:

$ sudo pip install memacs
Downloading/unpacking memacs
  Downloading memacs-0.3.tar.gz (53kB): 53kB downloaded
  Running setup.py (path:/tmp/pip_build_root/memacs/setup.py) egg_info for package memacs

Downloading/unpacking PIL (from memacs)
  Could not find any downloads that satisfy the requirement PIL (from memacs)
  Some externally hosted files were ignored (use --allow-external PIL to allow).
Cleaning up...
No distributions at all found for PIL (from memacs)
Storing debug log for failure in /root/.pip/pip.log

I can work around this with pip install memacs --allow-external PIL --allow-unverified PIL but could you move to pillow instead? https://github.com/python-imaging/Pillow It's actively maintained and a drop-in replacement for PIL.

novoid commented 10 years ago

I migrated from PIL to Pillow and published Memacs v0.4 with it. Please test and report issues.

Thanks for the hint!

nmsalgueiro commented 10 years ago

This will probably be a stupid question but are there plans to "port" Memacs fully into Emacs Lisp? I dream of a day when all it takes is to type a M-x list-packages, load it and then configure it on .emacs. In my simplistic way of looking at it, it would make sense because Emacs is already Memacs' platform, but there must be other more powerful reasons why such didn't happen.

novoid commented 10 years ago

No stupid question at all! :-)

The reason we used Python instead of Elisp was, that we've got no Elisp knowledge but Python knowledge. We are using GNU/Emacs as advanced users and wanted to become Memacs reality with our possibilities.

So please feel free to re-implement Memacs in Elisp!

Another benefit is that other users of Emacs without Elisp knowledge are able to code additional modules by themselves since Python-knowledge is far more widespread than Elisp knowledge.