From: kf <gebser@mousecar.com>
To: help-gnu-emacs@gnu.org
Subject: Re: In search for an emacs hacker
Date: Mon, 6 Sep 2021 14:30:37 -0400 [thread overview]
Message-ID: <978b2733-db34-b818-92b9-aaf4e9cddaf4@mousecar.com> (raw)
In-Reply-To: <a1405b57-a990-254b-fb3d-4b58561c83fe@uni-muenster.de>
On 9/6/21 11:52 AM, Vitus Schäfftlein wrote:
> I am looking for someone who is willing to help me with my project and
> some things I would like to have changed for my own sake. Of course,
> they will be paid, but I am a student paying out of his own pocket so my
> financial resources are limited (i can send you 150$ for a bigger task,
> but not 1500$...).
Yeah, after reading that, I knew you couldn't be an American college
student. Most of them can barely afford to buy books and Ramen noodles,
never to hire a programmer. :D
I love the idea you have. Unfortunately, I'm not much of an elisp
hacker (though I have written a few nice functions that have been
extremely useful over the years). I would suggest (1) finding some
webspace for your project... I'll let others make suggestions for that.
And (2), on that webspace make a prioritized list of the functions you
want (describing the functionality well)... and ask about them here on
this list too. You may find that there are the same or similar
functions already available in the vast emacs code base. And as the
FOSS developers say, "there's no sense in re-inventing the wheel."
As your project develops, you'll be able to move items on your "todo"
list to your "done" list and thereby document your academic-emacs project.
Viel Glück,
kf
next prev parent reply other threads:[~2021-09-06 18:30 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 [this message]
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=978b2733-db34-b818-92b9-aaf4e9cddaf4@mousecar.com \
--to=gebser@mousecar.com \
--cc=help-gnu-emacs@gnu.org \
/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).