search

lem-project / lem

Common Lisp editor/IDE with high expansibility
http://lem-project.github.io/
MIT License
2.39k stars 175 forks source link

Lem in quicklisp? #359

Closed gregcman closed 4 years ago

gregcman commented 5 years ago

Can we have lem in quicklisp?

jessymilare commented 5 years ago

I'll drop xcb. @jessymilare which system would you like to edit?

All systems that reported The name "LEM" does not designate any package or similar. The fix is to add "lem-core" in :depends-on. That means all contrib systems plus lem-setlocale, lem-selection-mode and lem-calc-mode.

snmsts commented 5 years ago

@jessymilare I guess I'm done.

phoe commented 5 years ago

@snmsts Let Xach know in the issue on quicklisp-projects - he'll redo the build and see if everything compiles now.

jessymilare commented 5 years ago

@jessymilare I guess I'm done.

@snmsts Is any of the .asd files auto-generated? If not, there is no reason for the "don't edit" comment in the first line and the problem is very simple to solve.

jessymilare commented 5 years ago

By the way, IMHO, if a file is auto-generated, it shouldn't be source. That makes the project less maintainable and more confusing.

gregcman commented 4 years ago

This seems to be moving along quite slowly, so I'm forking lem to put on quicklisp. It will be called "minilem" and will remove all the extra modes and contrib files and backends, leaving only the base text editor.

gregcman commented 4 years ago

If anyone is interested, its here

svetlyak40wt commented 4 years ago

@gmasching why do you want to have Lem in Quicklisp?

IMHO it is better to work on packaging for OSX, Ubuntu, etc.

gregcman commented 4 years ago

Because it's extremely simple to distribute lisp code that way. Just one function call and you have lem set up. This is important if you want new users. I'd like to use ultralisp but the .asd files have to be placed in the root directory, and that is a lot of refactoring. I'd be happy to help out solve this problem.

phoe commented 4 years ago

and that is a lot of refactoring

AFAIK you can move all ASD files to the main directory and then add :pathname "foo/bar/" to each of them for the new source location to be recognized.

Nonetheless, you shouldn't need to do that - Ultralisp should be able to scan the repository's structure and discover ASD systems even in nested directories, since ASDF already does that on its own.

gregcman commented 4 years ago

@phoe wow really? That would have made this process so much easier. Thank you for clarifying. I guess it wasn't a problem after all...

phoe commented 4 years ago

See https://github.com/mfiano/pngload-fast/blob/master/pngload-fast.asd for example.

(asdf:defsystem #:pngload-fast
  ...
  :pathname "src"
  ...
  ((:file "package") ;; refers fo src/package.lisp
   ...
   ))
svetlyak40wt commented 4 years ago

Ultralisp should process nested asd files, but it does not. It was turned off because some projects have broken nested asd files. Either they are examples or some tests or third party libraries bundled into the repository.

I'm aware of this problem and hope somebody will help to add a project-level setting to set up an ignore list. After that, the loading of the nested asd files can be enabled by default.