Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
Lower the barrier to entry, maybe give them your configuration or some sort of starter-kit, I think castlemacs is good choice as it is quite simple and useable. Tell them to fork it on Github and use it.
I guess, to start with, it is best to answer for yourself why you would recommend users to use Emacs. Even better if you write it down for yourself, so that you could publish it as a blog post (in org-mode). If they are coding in some particular language, then also explain your optimal workflow for that language. E.g. when you are teaching python, then tell them how to use the inferior-shell and send code to it. Or maybe how to use ipython notebooks or emacs jupyter. Or when coding C, explain how to use Makefile's or quickrun. I guess if you recommend Emacs, you expect them to learn some elisp (I would never recommend users to use Emacs without learning some elisp). Tell them that elisp is more fun than it looks initially, and it isalmost as easy as e.g. python. Possibly show how to use basic magit, and org-mode and definitely tell them about evil and Spacemacs/Doom (or other starter kits). In the end, simply try to motivate your enthusiasm and offer a helping hand. But accept that (some) users have no need/time for it. Then second, use the answers here to improve your 'inspirational talk/writing'...
I guess, to start with, it is best to answer for yourself why you would recommend users to use Emacs. Even better if you write it down for yourself, so that you could publish it as a blog post (in org-mode). If they are coding in some particular language, then also explain your optimal workflow for that language. E.g. when you are teaching python, then tell them how to use the inferior-shell and send code to it. Or maybe how to use ipython notebooks or emacs jupyter. Or when coding C, explain how to use Makefile's or quickrun. I guess if you recommend Emacs, you expect them to learn some elisp (I would never recommend users to use Emacs without learning some elisp). Tell them that elisp is more fun than it looks initially, and it isalmost as easy as e.g. python. Possibly show how to use basic magit, and org-mode and definitely tell them about evil and Spacemacs/Doom (or other starter kits). In the end, simply try to motivate your enthusiasm and offer a helping hand. But accept that (some) users have no need/time for it. Then second, use the answers here to improve your 'inspirational talk/writing'...
I guess, to start with, it is best to answer for yourself why you would recommend users to use Emacs. Even better if you write it down for yourself, so that you could publish it as a blog post (in org-mode). If they are coding in some particular language, then also explain your optimal workflow for that language. E.g. when you are teaching python, then tell them how to use the inferior-shell and send code to it. Or maybe how to use ipython notebooks or emacs jupyter. Or when coding C, explain how to use Makefile's or quickrun. I guess if you recommend Emacs, you expect them to learn some elisp (I would never recommend users to use Emacs without learning some elisp). Tell them that elisp is more fun than it looks initially, and it isalmost as easy as e.g. python. Possibly show how to use basic magit, and org-mode and definitely tell them about evil and Spacemacs/Doom (or other starter kits). In the end, simply try to motivate your enthusiasm and offer a helping hand. But accept that (some) users have no need/time for it. Then second, use the answers here to improve your 'inspirational talk/writing'...