Thoughts about support #1066
Replies: 4 comments 2 replies
-
Hi Blake McBride. I am glad you are interesting in lem. I am sorry that the questions I wrote in the discord were not answered. One of lem's goals is documentation. I would be honored if we could improve lem together. |
Beta Was this translation helpful? Give feedback.
-
Knowing that you had to be in the scripts directory for the build to work was unclear to me. I was unable to build the system until I stumbled upon that fact. |
Beta Was this translation helpful? Give feedback.
-
Hmm, I don't think that's necessary. |
Beta Was this translation helpful? Give feedback.
-
Hi there,
for the matter we are in the right direction 😎 After Lem 2.0, we (new users/devs) quickly put up this website: https://lem-project.github.io/lem-page/ for how to use Lem. At least, we now have a list of features and keybindings ;) There's a little M-x help, there's still the github wiki, and various people helped to translate much if not all docstrings in japanese. So, the situation has progressed, there is some infrastructure for more. Personally, I think that for the time being, installation instructions are well placed in the README and issues. I also use questions asked on Discord to augment the manual.
I can see one question indeed. I believe most of us didn't know the answer nor if it was possible at all as of today (we should have added an emoji to show you that we read the question). In your situation, I would ask on a Github discussion or issue. (I view Discord as a first means to not overcharge github issues and the pressure on devs, and github as the ultimate place to ask something). => I'd encourage you to try again before forging your final opinion.
yay, that would be great indeed. That being said, of course the community is tiny. But already quite diverse I would say.
Would you like to contribute to the website? Any more prose is welcome, and help on how to develop in other languages with the LSP. We could also generate an EPUB from the pages. Ultimately, we'll need to publish some technical documentation, extracted from the sources, or a high-level manual for developers (there's the tiny this and this) . Presently, lisp developers -not users- can navigate quite well Lem's code base.
Isn't Lem easy to grok for Emacs users? They'd try M-x and explore from there. |
Beta Was this translation helpful? Give feedback.
-
Greetings,
I'm just offering some opinions from the outside.
I like the idea of lem a great deal. I have been using GNU Emacs for more than 20 years and am a big fan of Lisp. I have long desired an emacs based on Common Lisp that catered to the Lisp community. Lem is exciting!
I use GNU Emacs daily. Unfortunately, I do not get to do much with lisp. In spite of this, however, I would like to completely switch from GNU Emacs to lem.
There is, however, one big thing holding me back - support. I have questions about the use and customization of lem. I tried Discord but got no response. There is no manual, and the notes are very limited, random, and scattered. If I was able to get timely answers to questions, I might even be interested in writing a manual!
I'd really like to see lem widely adopted, but I fear without a user manual, lem will be relegated to just a few "experts" who are willing to devote significant effort to understanding the platform.
Beta Was this translation helpful? Give feedback.
All reactions