Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #178947

Re: Suitable text editor [NOT word processor] or workaround?

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Thu, Mar 16, 2017 at 09:54:42AM -0400, Gene Heskett wrote:
> gedit has caused me to have to start over again, 3 times, on a 600+ line 
> configuration file for machine control on several occasions. As the file 
> it trashed was 6 months worth of adding new features to that machines 
> control, that was not appreciated. 1st time is a wtf?, 2nd time sends me 
> a message, 3rd time I shut it down w/o the save and never ran it again.

Whilst this is very frustrating, one other thing it tells me is you need
to set up a backup system (although you are quite right to abandon gedit
based on your experiences)

> gedit is like asking if freshly poured concrete will crack.  Wrong 
> question because it will, the right question is "when", its just a 
> matter of time. Life is too short for putting up with that.

I like this comparison :)

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Suitable text editor [NOT word processor] or workaround? Richard Owlett <rowlett@cloud85.net> - 2017-03-16 12:40 +0100
  Re: Suitable text editor [NOT word processor] or workaround? Celejar <celejar@gmail.com> - 2017-03-16 13:10 +0100
    Re: Suitable text editor [NOT word processor] or workaround? Richard Owlett <rowlett@cloud85.net> - 2017-03-16 14:30 +0100
    Re: Suitable text editor [NOT word processor] or workaround? Gene Heskett <gheskett@shentel.net> - 2017-03-16 15:00 +0100
      Re: Suitable text editor [NOT word processor] or workaround? Jonathan Dowland <jmtd@debian.org> - 2017-03-17 10:50 +0100
        Re: Suitable text editor [NOT word processor] or workaround? Gene Heskett <gheskett@shentel.net> - 2017-03-17 12:40 +0100
          Re: Suitable text editor [NOT word processor] or workaround? Jonathan Dowland <jmtd@debian.org> - 2017-03-17 15:30 +0100
            Re: Suitable text editor [NOT word processor] or workaround? Gene Heskett <gheskett@shentel.net> - 2017-03-17 15:50 +0100
    Re: Suitable text editor [NOT word processor] or workaround? Ben Caradoc-Davies <ben@transient.nz> - 2017-03-16 23:30 +0100
  Re: Suitable text editor [NOT word processor] or workaround? Lisi Reisz <lisi.reisz@gmail.com> - 2017-03-16 13:10 +0100
    Re: Suitable text editor [NOT word processor] or workaround? Richard Owlett <rowlett@cloud85.net> - 2017-03-16 14:30 +0100
  Re: Suitable text editor [NOT word processor] or workaround? <tomas@tuxteam.de> - 2017-03-16 13:20 +0100
    Re: Suitable text editor [NOT word processor] or workaround? John Hasler <jhasler@newsguy.com> - 2017-03-16 14:00 +0100
    Re: Suitable text editor [NOT word processor] or workaround? Richard Owlett <rowlett@cloud85.net> - 2017-03-16 14:40 +0100
      Re: Suitable text editor [NOT word processor] or workaround? <tomas@tuxteam.de> - 2017-03-16 14:50 +0100
        Re: Suitable text editor [NOT word processor] or workaround? rhkramer@gmail.com - 2017-03-16 15:10 +0100
          Re: Suitable text editor [NOT word processor] or workaround? Christian Groessler <chris@groessler.org> - 2017-03-16 15:50 +0100
            Re: Suitable text editor [NOT word processor] or workaround? rhkramer@gmail.com - 2017-03-16 17:50 +0100
          Re: Suitable text editor [NOT word processor] or workaround? John Hasler <jhasler@newsguy.com> - 2017-03-16 17:40 +0100
  Re: Suitable text editor [NOT word processor] or workaround? Andreas Ronnquist <mailinglists@gusnan.se> - 2017-03-16 13:30 +0100
    Re: Suitable text editor [NOT word processor] or workaround? Andreas Ronnquist <mailinglists@gusnan.se> - 2017-03-16 13:30 +0100
      Re: Suitable text editor [NOT word processor] or workaround? Richard Owlett <rowlett@cloud85.net> - 2017-03-16 15:00 +0100
        Re: Suitable text editor [NOT word processor] or workaround? Andreas Ronnquist <mailinglists@gusnan.se> - 2017-03-16 15:30 +0100
  Re: Suitable text editor [NOT word processor] or workaround? Joe <joe@jretrading.com> - 2017-03-16 13:30 +0100
    Re: Suitable text editor [NOT word processor] or workaround? Richard Owlett <rowlett@cloud85.net> - 2017-03-16 15:10 +0100
      Re: Suitable text editor [NOT word processor] or workaround? Joe <joe@jretrading.com> - 2017-03-16 19:20 +0100
  Re: Suitable text editor [NOT word processor] or workaround? John Hasler <jhasler@newsguy.com> - 2017-03-16 14:00 +0100
    Re: Suitable text editor [NOT word processor] or workaround? davidson@freevolt.org - 2017-03-17 20:20 +0100
      Re: Suitable text editor [NOT word processor] or workaround? davidson@freevolt.org - 2017-03-17 20:50 +0100
  Re: Suitable text editor [NOT word processor] or workaround? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-03-16 14:40 +0100
  Re: Suitable text editor [NOT word processor] or workaround? Fred <fred@blakemfg.com> - 2017-03-16 15:20 +0100
    Re: Suitable text editor [NOT word processor] or workaround? Ben Caradoc-Davies <ben@transient.nz> - 2017-03-16 23:20 +0100
  Re: Suitable text editor [NOT word processor] or workaround? Charlie Kravetz <cjk@teamcharliesangels.com> - 2017-03-16 15:50 +0100
  Re: Suitable text editor [NOT word processor] or workaround? cbannister@slingshot.co.nz - 2017-04-01 18:00 +0200
    Re: Suitable text editor [NOT word processor] or workaround? Richard Owlett <rowlett@cloud85.net> - 2017-04-01 18:30 +0200
      Re: Suitable text editor [NOT word processor] or workaround? Fred <fred@blakemfg.com> - 2017-04-01 21:40 +0200
        Re: Suitable text editor [NOT word processor] or workaround? Tom Browder <tom.browder@gmail.com> - 2017-04-02 13:20 +0200
      Re: Suitable text editor [NOT word processor] or workaround? Curt <curty@free.fr> - 2017-04-02 13:30 +0200
    Re: Suitable text editor [NOT word processor] or workaround? Curt <curty@free.fr> - 2017-04-01 18:50 +0200

csiph-web