Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #178903
| From | <tomas@tuxteam.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Suitable text editor [NOT word processor] or workaround? |
| Date | 2017-03-16 13:20 +0100 |
| Message-ID | <tlCxP-6BJ-7@gated-at.bofh.it> (permalink) |
| References | <tlBV7-62w-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Mar 16, 2017 at 06:38:52AM -0500, Richard Owlett 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.
>
> 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.
This nearly sounds like a description of Emacs' ediff mode.
That said, Emacs is sufficiently different from the text editors
around that tackling it amounts to taking a respectable hill.
The view from up there, though, is breathtaking.
Some tricks in the rough context of system administration:
- transparent editing of files on other hosts, given only
one of ssh/sftp/ftp access (tramp).
- mixed marked-up text (à la Markdown) and code snippets,
inserting the "result" of evaluating those code snippets
in the text (code == C, Python, Perl, shells, R, many
more), results can be text or images, for documenting
(up to literary programming)
- useful exploration of lots of files. The idiom of
"find . -type f -name *blah -exec grep foo {} +"
from your editor, with clickable links to the found
lines
- hex editor, psychotherapist, towers of Hanoi ;-)
> Suggestions?
That said, it takes some investment. Some would say it's a
religion, but there are especially perverse polyreligious
folks out there: I "am" Vim *and* Emacs (take that ;-)
regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAljKgVcACgkQBcgs9XrR2kYjkgCdGos4ETw/d/wbjamy/7/vDUjY
GtAAmgJliKRpwYucxh7iRBroqaQMlsWJ
=3e/X
-----END PGP SIGNATURE-----
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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