From: shentino@gmail.com (Raymond Jennings)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Developing environments used for kernel development
Date: Fri, 25 Dec 2015 09:14:15 -0800 [thread overview]
Message-ID: <1451063655.29678.0@smtp.gmail.com> (raw)
In-Reply-To: <CAF3SDA4YQ-=oA3CN21uG=-gXJx_EmmyqROn+BJDLmhVMg8vJMg@mail.gmail.com>
On Tue, Dec 22, 2015 at 11:27 AM, Daniel. <danielhilst@gmail.com> wrote:
> My boss came to my desk today raiging that I should use more
> productive tools for developing. Well I don't want to begin an editor
> war but, yes, I use emacs. I used to use vim before but the
> integration of emacs and gdb has caught my attention.
>
> To be clear, as "more productive tools" he understands graphical eye
> candy tools. My argument to use an "simple editor plus makefiles"
> was, it just works and thats it. So before to downloading eclipse
> just to make my boss's eyes happy I've decided to make a little
> research.
>
> What you guys are using today to develope kenrel code?
While in virtual console, I use midnight commander's built in editor
for the bulk of my actual dev work.
Then when I need to email anything, I switch to gui and use gedit to
open the file, copy it to the clipboard, and paste it into my email
client for patch delivery.
My criteria is "hold the text and stay the hell out of my way. Be a
tool and don't try to do my thinking for me."
> Best Regards,
> - dhs
>
> --
> "Do or do not. There is no try"
> Yoda Master
next prev parent reply other threads:[~2015-12-25 17:14 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 19:27 Developing environments used for kernel development Daniel.
[not found] ` <CAJX_Q+2AOXLM=XWsSYzUbpG=MKH+p2D1Xf2k7xGFrQdn=_zPTQ@mail.gmail.com>
2015-12-22 21:26 ` Daniel.
2015-12-22 21:43 ` Lucas Tanure
2015-12-22 22:41 ` Daniel.
2015-12-22 22:15 ` Clemens Gruber
2015-12-23 0:06 ` Daniel.
2015-12-24 11:59 ` Andrey Skvortsov
2015-12-24 13:57 ` Daniel.
2016-01-14 0:23 ` Ismael Luceno
2016-01-14 0:37 ` Geyslan G. Bem
2016-01-14 13:06 ` Daniel.
2016-01-14 13:53 ` Geyslan G. Bem
2016-01-14 14:26 ` Geyslan G. Bem
2016-01-14 15:23 ` Daniel.
2016-01-14 15:35 ` Geyslan G. Bem
2016-01-14 16:28 ` Daniel.
2016-01-14 16:28 ` Daniel.
2016-01-14 16:36 ` Geyslan G. Bem
2016-01-14 16:52 ` Daniel.
2016-01-14 16:58 ` Geyslan G. Bem
2015-12-24 15:41 ` Ruben Safir
2015-12-24 17:33 ` Daniel.
2015-12-24 18:43 ` Valdis.Kletnieks at vt.edu
2015-12-24 20:13 ` Manuel Pégourié-Gonnard
2015-12-25 0:29 ` Ruben Safir
2015-12-25 0:52 ` Valdis.Kletnieks at vt.edu
2015-12-25 1:42 ` Ruben Safir
[not found] ` <4E5779AD88B2F040B8A7E83ECF544D1A64AC5F@SJCPEX01CL03.citrite.net>
2015-12-23 1:18 ` Daniel.
2015-12-23 13:30 ` Daniel.
2015-12-23 14:45 ` amit mehta
2015-12-23 17:20 ` Daniel.
2016-01-14 19:19 ` Geyslan G. Bem
2016-01-14 20:08 ` Daniel.
2015-12-25 17:14 ` Raymond Jennings [this message]
2015-12-28 12:28 ` Daniel.
2015-12-28 12:57 ` Manuel Pégourié-Gonnard
2015-12-28 14:05 ` Fernando Apesteguía
2015-12-28 19:11 ` Daniel.
2015-12-29 5:10 ` Daniel.
2015-12-29 9:50 ` Manuel Pégourié-Gonnard
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=1451063655.29678.0@smtp.gmail.com \
--to=shentino@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 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.