Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #26311
| From | Tauno Voipio <tauno.voipio@notused.fi.invalid> |
|---|---|
| Newsgroups | sci.electronics.design, comp.arch.embedded |
| Subject | Re: Codewright Failure |
| Date | 2017-03-27 19:41 +0300 |
| Organization | A noiseless patient Spider |
| Message-ID | <obbf68$op5$1@dont-email.me> (permalink) |
| References | (6 earlier) <u6kbdch7vasta94egi3hvesk0ndhr4sj46@4ax.com> <ob6gsu$rau$2@dont-email.me> <obaguf$d9h$1@dont-email.me> <obaspd$kcm$1@dont-email.me> <obauob$qtj$1@dont-email.me> |
Cross-posted to 2 groups.
On 27.3.17 15:01, David Brown wrote: > On 27/03/17 13:27, Tauno Voipio wrote: >> On 27.3.17 11:05, David Brown wrote: >> >>> If you want to work directly with a Pi, get a Pi 3 - the earlier ones >>> are a bit too slow for using as a desktop. (They are great for running >>> specific programs, but it gets painful when it takes a few seconds to >>> open a new large program.) I find it is easier to do most stuff from a >>> PC, and only occasionally edit things directly on a Pi. But that is >>> easier if the desktop is Linux, since it gives you several convenient >>> ways to swap files and work together with the Pi. >>> >>> So for an editor that works on the Pi, I usually use nano. It is a >>> simple command-line editor - fine for making small fixes, and works well >>> over ssh even on very limited connections. Unlike other popular >>> command-line editors such as vi and emacs, it works as you would expect >>> it to. >>> >>> As for an editor for Linux and/or Windows, I am afraid you are in >>> trouble - there are vast numbers of them, with a broad range from light >>> and simple to large and complex. They are all somewhat different from >>> Codewright - and it is always hard for a "power user" to switch editors. >>> No matter which editor you pick, you will go through a period where you >>> feel there are missing features, bad layouts, counter-intuitive >>> interfaces, etc., simply because it is not the editor you are so >>> familiar with. >>> >>> Personally, I use eclipse as my main editor these days, on Linux and >>> Windows. It works well for what I need, I am used to it, and it is by >>> far the most common IDE delivered with microcontroller toolchains. But >>> I would not run it on a Pi, and I fully understand how some people don't >>> like it. >> >> >> Another vote for Eclipse, but it is large to huge, depending on >> how many features are included. >> >> Hardcore Unix people swear by Emacs. It seems to include everything >> but a kitchen sink. >> > > Hardcore unix people are divided into three camps here. Those who live > entirely within emacs (including for email, and as their Usenet reader), > those who think emacs is the work of the devil and the only real editor > is vim, and those who believe there were perfectly usable gui desktops > for *nix by the late 1980's, and believe they can give you more > productive editors than a 80x40 terminal screen. The last group (like me) are indeed heretics, but I do not miss Flexowriter, ASR-33 or any glass equivalent. -- -TV
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Codewright Failure rickman <gnuarm@gmail.com> - 2017-02-16 17:17 -0500
Re: Codewright Failure John Speth <johnspeth@yahoo.com> - 2017-02-16 18:18 -0800
Re: Codewright Failure rickman <gnuarm@gmail.com> - 2017-02-16 21:36 -0500
Re: Codewright Failure John Speth <johnspeth@yahoo.com> - 2017-02-17 10:11 -0800
Re: Codewright Failure rickman <gnuarm@gmail.com> - 2017-03-24 15:40 -0400
Re: Codewright Failure John Speth <johnspeth@yahoo.com> - 2017-03-24 12:54 -0700
Re: Codewright Failure rickman <gnuarm@gmail.com> - 2017-03-24 16:10 -0400
Re: Codewright Failure George Neuner <gneuner2@comcast.net> - 2017-03-24 22:50 -0400
Re: Codewright Failure rickman <gnuarm@gmail.com> - 2017-03-25 15:39 -0400
Re: Codewright Failure George Neuner <gneuner2@comcast.net> - 2017-03-26 04:55 -0400
Re: Codewright Failure David Brown <david.brown@hesbynett.no> - 2017-03-27 10:05 +0200
Re: Codewright Failure Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2017-03-27 14:27 +0300
Re: Codewright Failure David Brown <david.brown@hesbynett.no> - 2017-03-27 14:01 +0200
Re: Codewright Failure Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2017-03-27 19:41 +0300
Re: Codewright Failure "David Eather" <eather@tpg.com.au> - 2017-02-18 23:12 +1000
Re: Codewright Failure "David Eather" <eather@tpg.com.au> - 2017-02-18 23:13 +1000
Re: Codewright Failure mrfirmware <mrfirmware@gmail.com> - 2017-03-22 09:32 -0700
Re: Codewright Failure "roricka" <137631@EmbeddedRelated> - 2019-08-01 14:09 -0500
Re: Codewright Failure Rick C <gnuarm.deletethisbit@gmail.com> - 2019-08-01 15:51 -0700
Re: Codewright Failure Rick C <gnuarm.deletethisbit@gmail.com> - 2019-08-10 15:30 -0700
Re: Codewright Failure John Speth <johnspeth@yahoo.com> - 2019-08-02 21:33 -0700
Re: Codewright Failure quantumankh@gmail.com - 2020-02-09 22:17 -0800
csiph-web