unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: In search for an emacs hacker
Date: Mon, 06 Sep 2021 20:11:31 +0200	[thread overview]
Message-ID: <87y289mv58.fsf@zoho.eu> (raw)
In-Reply-To: 8735qhoamn.fsf@zoho.eu

Vitus Schäfftlein wrote:

> For this reason, I want to create my own blog on which
> I explain how to use emacs as an academic. Now these people
> aren't emacs programmers and neither am I (I know how to set
> variables, key-bind functions, and some very basic lisp, but
> that's it), so my goal is to (1) provide simple
> step-by-step-instructions to get everything running smoothly
> and (2) describe in detail how an emacs workflow for
> academics can look like. My big dream is to eventually
> create something like doom emacs or spacemacs, but for
> academics. Functions and key-bindings should closely
> resemble those of programs academics usually use.

I have another idea, we fork Emacs into "Creamacs", which will
be basically the same, only it would be more of an
elite thing.

You know high society, is that the reasons so few are here and
use Emacs? They _want to_ but think, "Darn, all these
plebeians are just using Emacs all day every day, if I do the
same they'd think, 'hey, these disgusting aristos are even
using the same software!', there'd be just nothing to
really motivate patrician rule anymore!"

But with Creamacs, it would be the A Camp ONLY!

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2021-09-06 18:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06 15:52 In search for an emacs hacker Vitus Schäfftlein
2021-09-06 17:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-06 18:11   ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-09-06 18:30 ` kf
2021-09-06 18:38   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-06 23:39   ` [External] : " Drew Adams
2021-09-07  2:10     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-07  7:39       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-06 19:09 ` Arthur Miller
2021-09-06 19:17   ` Samuel Banya
2021-09-07  2:07     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-07 17:41       ` Samuel Banya
2021-09-24  5:44     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-24  5:42   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-06 19:09 ` Daniel Fleischer
2021-09-06 19:28 ` Eduardo Ochs
  -- strict thread matches above, loose matches on Subject: below --
2021-09-12 12:54 Vitus Schäfftlein
2021-09-13  9:24 ` Arash Esbati
2021-09-24  6:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-24  6:07   ` Thibaut Verron
2021-09-24  6:37     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-12 13:01 Vitus Schäfftlein
2021-09-12 13:15 Vitus Schäfftlein

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y289mv58.fsf@zoho.eu \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).