unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Arthur Miller <arthur.miller@live.com>
To: "Vitus Schäfftlein" <v_scha12@uni-muenster.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: In search for an emacs hacker
Date: Mon, 06 Sep 2021 21:09:13 +0200	[thread overview]
Message-ID: <AM9PR09MB497710945FC7472EEF1C532E96D29@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <a1405b57-a990-254b-fb3d-4b58561c83fe@uni-muenster.de> ("Vitus Schäfftlein"'s message of "Mon, 6 Sep 2021 17:52:43 +0200")

Vitus Schäfftlein <v_scha12@uni-muenster.de> writes:

> Hey, folks!
>
> tl;dr looking to hire an emacs hacker who helps me change emacs to make it work
> for academics.

Have you tried Scimax? https://github.com/jkitchin/scimax

It is done by an academic (John Kitchin) for use in science. It runs well on
Windows and maybe already does what you need?

> Is there an emacs hacker out here who is convinced that emacs should be used by
> academics, too, and who wants to support this cause while earning some money on
> the way? If so, please get in touch with me!

I think that all Emacs hackers are convinced that Emacs should work for
academics and for everyone else for that matter.

If you find functions that does not work as expected, than repport bugs. That
will definitely help develop Emacs.

Also use this list and r/Emacs (Emacs on Reddit) and ask for help about tasks
you are doing. The more you do yourself the more you will learn.

If you would like to hire someone than sure post on emacs-devel@gnu.org or on
r/Emacs, I am sure someone will help you.

It will probably help if you post the problem you would like solved first.

best regards



  parent reply	other threads:[~2021-09-06 19:09 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
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 [this message]
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=AM9PR09MB497710945FC7472EEF1C532E96D29@AM9PR09MB4977.eurprd09.prod.outlook.com \
    --to=arthur.miller@live.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=v_scha12@uni-muenster.de \
    /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).