From: Federico Tedin <federicotedin@gmail.com>
To: emacs-devel@gnu.org
Subject: Questions about developing Emacs
Date: Wed, 5 Feb 2020 18:40:18 +0100 [thread overview]
Message-ID: <CAA8GjPn883WgDE5TDOpYw6tfvf7awtfpgFNjdBmwJ6nOSQB6gg@mail.gmail.com> (raw)
Hi all,
Over the past year and a half (~) I've started using Emacs, and at the
same time have been trying to improve it by fixing and/or adding stuff
from the bug tracker. I've managed to reach a workflow that more or
less works for me, but I think there's still a lot of room for
improvement. So here's a couple of questions that I have for anyone
interested in providing some advice:
- Will replies to older bugs (say, 1 or 2 years old) still get noticed
by the maintainers? I'm not sure how the visibility for this works. I
usually tend to look for bugs without any replies (that I believe I
can fix), but sometimes no recent ones are available, so I have to
look further back.
- Is there any way to find bugs that will involve more C coding? I'm
interested in improving that set of skills, but most bugs/additions
seem to require much more Elisp coding.
- What's the best way of moving from fixing small things, onto
adding/modifying larger parts of how Emacs works? I imagine that this
greatly depends on the amount of time spent working on the project.
Thanks in advance for any answers or comments.
- Fede
next reply other threads:[~2020-02-05 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 17:40 Federico Tedin [this message]
2020-02-05 17:48 ` Questions about developing Emacs Eli Zaretskii
2020-02-06 1:05 ` Federico Tedin
2020-02-06 2:23 ` Stefan Monnier
2020-02-06 22:06 ` Federico Tedin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA8GjPn883WgDE5TDOpYw6tfvf7awtfpgFNjdBmwJ6nOSQB6gg@mail.gmail.com \
--to=federicotedin@gmail.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.