Re: Some developement questions

[hw]

Eli Zaretskii <address@hidden> writes:

> [...]
>> >Emacs is much more flexible, and different people have different
>> >needs.
>> >
>> Yes, but someone who opens emacs for the first time will open it to edit 
>> text and very probably to program, he
>> should have color preferences and for sure he doesn't know how to add 
>> packages and the elpa repository
>> (maybe don't even know about about something called elpa), so, the most 
>> basic customization options. If
>> comes from vim/nano/gedit he will need some assistance that emacs can bring 
>> (not only the tutorial, but
>> evile, bindkeys), but he don't know how get there. Maybe he prefers to use 
>> always the terminal version instead
>> of the graphical one, or he will read the manual and something keybinds 
>> doesn't work, and blame emacs
>> when tmux was the guilty. 
>
> Exactly my point: you have just enumerated at least 3 different
> classes of users, and the solution is different for every one of them.
> Finding a way of being friendly to each class is the problem to solve.
> One possible solution could be groups of Custom options that are
> likely to be relevant to each class of users, and writing
> customization commands that target each class.  Patches are welcome.

How about including a number of ~/.emacs files, containing options
supposed to make things easier for a class of users --- or include
groups of ~/.emacs files so that for any given class, there can be many
configurations to pick from within a group?

Maybe that can (needs to) be done with existing package management,
including the things users have written themselves and use with their
configurations.

It would also make a great resource for learning.

>> BTW: Whats the best documentation (from
>> scratch) to learn elisp and the emacs developement environment? Do you have 
>> anything like for example:
>> "The Linux Programming Interface" from "Michael Kerrisk" but for Emacs? 
>
> Take a look at Introduction to Programming in Emacs Lisp, it comes
> with Emacs.

That would be my recommendation, too, plus elisp written by others.