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

Groups > linux.debian.user > #178920

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

From Richard Owlett <rowlett@cloud85.net>
Newsgroups linux.debian.user
Subject Re: Suitable text editor [NOT word processor] or workaround?
Date 2017-03-16 15:10 +0100
Message-ID <tlEgh-7RT-7@gated-at.bofh.it> (permalink)
References <tlBV7-62w-15@gated-at.bofh.it> <tlCHv-6I6-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On 03/16/2017 07:20 AM, Joe wrote:
> On Thu, 16 Mar 2017 06:38:52 -0500
> Richard Owlett <rowlett@cloud85.net> wrote:
>
>> My environment is Jessie (8.6.0) with MATE desktop.
>> I require two things:
>>   1. a search and replace which can include a "newline" in new string.
>>   2. display/edit 2 files simultaneously *side by side*
>>
>> MATE's standard editor (Pluma) can handle the first easily.
>>
>> I see no way to open 2 instances of Pluma in separate windows - a la
>> Notepad in WindowsXP. Pluma will only open multiple files in multiple
>> tabs.
>
> So will gedit, but have you tried right-clicking and seeing if you get
> 'open in another window' as gedit does?

The version I have does not, but evidently the latest does.

>>
>> The two files are nearly identical and need them displayed
>> simultaneously for instant visual comparison. Opening one of the
>> files read only would be acceptable but not preferable.
>>
>
> Yes, that does suggest a programming tool such as geany, or a graphical
> file diff utility. I don't use one in Linux, but there are several.
> http://www.tecmint.com/best-linux-file-diff-tools-comparison/
>

I don't need a diff tool exactly. I need to do a _visual_ comparison 
make sure I'm editing the right portion.
I might say I was looking for an "analog" not "digital" solution.

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