A good Text Editor for Large Text Files
A good Text Editor for Large Text Files
A need a text editor that works from a random access file on disk rather than ram. The reason being is that the file is large and large text files seam to crash geany.
The following thread from stack overflow suggets:
https://askubuntu.com/questions/28847/t ... -text-file
joe, glogg, lfhex, Hed and 010 Editor, kinesics, bless, wxhexeditor, nedit and NetBeans. I don't think that all of these of for linux. I'm going to start from the beginning of the list.
Let me know if anyone recommends any of these.
For fatdog64 on gsplat wxhexeditor is available, so I'll try that one first.
https://askubuntu.com/questions/28847/t ... -text-file
joe, glogg, lfhex, Hed and 010 Editor, kinesics, bless, wxhexeditor, nedit and NetBeans. I don't think that all of these of for linux. I'm going to start from the beginning of the list.
Let me know if anyone recommends any of these.
For fatdog64 on gsplat wxhexeditor is available, so I'll try that one first.
Re: A good Text Editor for Large Text Files
What's a "random access file on disk"? How large is large?
Re: A good Text Editor for Large Text Files
Currently it is only 808M but it could be bigger. It depends on how fine I tune the logging and what the logging interval is. Also how much memory I have depends on what I'm running.phat7 wrote:What's a "random access file on disk"? How large is large?
So wxhexeditor seems to work but it is hard to read because it is a hex editor. Glogg is much better for my purposes. The slackbuild compiled with out issue on fatdog64 and is working. I might try compiling a few of the others then offering them for download.
I also was able to comple the slackbuild for nedit on fatdog64, it doesn't seem to render that well for me and it doesn't handle large files as well as glogg.
I also was able to comple the slackbuild for nedit on fatdog64, it doesn't seem to render that well for me and it doesn't handle large files as well as glogg.
- Colonel Panic
- Posts: 2171
- Joined: Sat 16 Sep 2006, 11:09
Have you tried vi or one of its derivatives? I was able to edit a 6 MB text file in GVim without any problems.
Last edited by Colonel Panic on Sun 30 Sep 2018, 09:29, edited 1 time in total.
Gigabyte M68MT-52P motherboard, AMD Athlon II X4 630, 5.8 GB of DDR3 RAM and a 250 GB Hitachi hard drive running Ubuntu 16.04.6, MX-19.2, Peppermint 10, PCLinuxOS 20.02, LXLE 18.04.3, Pardus 19.2, exGENT 200119, Bionic Pup 8.0 and Xenial CE 7.5 XL.
Excellent question, jafadmin.jafadmin wrote:To be clear, do you want to EDIT extremely large files, or VIEW them?
@s243a:
If only viewing, the tail utility has the < -f > setting, which "prints data as
the file grows". There is also good old less, which can read files of infinite
length and has a feature similar to tail.
About editing that 808 Mb file, you know about the split utility, yes? If you
find no editor to edit this extra big file, make a copy of it and split it in
smaller sections your editor can load.
Also, from my experience, I can tell you that the bigger the file, the slower
it is to move through it -- in any editor. So splitting is a good idea.
About text editors --
Here's a relatively new text editor worth trying, IMO: cudatext
(I have put geany on the shelf and now use cudatext instead.)
It doesn't mention about editing huge files, but it has:
From your list, "joe" (acronym for "Joe's Own Editor") is for linux.Binary/Hex viewer for files of unlimited size.
https://joe-editor.sourceforge.io
I have proposed a pet archive of its 4.1 version on this forum:
http://murga-linux.com/puppy/viewtopic. ... 201#891122
If that doesn't work on your Pup, please don't say it doesn't work? Tell me
the version of your Pup and I'll compile a joe editor just for you and your
Pup.
Joe is as versatile as geany, and it's been around for over 20 years (IIRC).
The only reason IMO that the joe editor is not getting more exposure is
that it is a CLI app -- and people are snobs!
Also the less reader can easily be interfaced with some text editors by
typing v in less. If you need this feature, I already have available a wrapper
that interfaces less with joe (or Geany, or TEA, but NOT leafpad); just ask.
(Or search this bazaar of a forum a bit: it's already here somewhere!)
IHTH
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
I'll give both joe and vi a try. Glogg works for this purpose and I created a fatdog64 package for it (using the slackbuild) (see post)musher0 wrote:Excellent question, jafadmin.jafadmin wrote:To be clear, do you want to EDIT extremely large files, or VIEW them?
@s243a:
If only viewing, the tail utility has the < -f > setting, which "prints data as
the file grows". There is also good old less, which can read files of infinite
length and has a feature similar to tail.
About editing that 808 Mb file, you know about the split utility, yes? If you
find no editor to edit this extra big file, make a copy of it and split it in
smaller sections your editor can load.
Also, from my experience, I can tell you that the bigger the file, the slower
it is to move through it -- in any editor. So splitting is a good idea.
About text editors --
Here's a relatively new text editor worth trying, IMO: cudatext
(I have put geany on the shelf and now use cudatext instead.)
It doesn't mention about editing huge files, but it has:From your list, "joe" (acronym for "Joe's Own Editor") is for linux.Binary/Hex viewer for files of unlimited size.
https://joe-editor.sourceforge.io
I have proposed a pet archive of its 4.1 version on this forum:
http://murga-linux.com/puppy/viewtopic. ... 201#891122
If that doesn't work on your Pup, please don't say it doesn't work? Tell me
the version of your Pup and I'll compile a joe editor just for you and your
Pup.
Joe is as versatile as geany, and it's been around for over 20 years (IIRC).
The only reason IMO that the joe editor is not getting more exposure is
that it is a CLI app -- and people are snobs!
Also the less reader can easily be interfaced with some text editors by
typing v in less. If you need this feature, I already have available a wrapper
that interfaces less with joe (or Geany, or TEA, but NOT leafpad); just ask.
(Or search this bazaar of a forum a bit: it's already here somewhere!)
IHTH
Bless is worse for overhead because it depends on mono!musher0 wrote:Yes, but those are 64-bit apps.
About Glogg:
The Glogg welcome page says it is a combination of grep and less. (Hint, hint.)
Plus Glogg is a Qt app. Wow, the overhead...
Just my 2 ¢.
QT doesn't concern me because I install it on every puppy.
Thanks for the hints though Maybe we could make a gtkdialog version of glogg or maybe a geany plugin that does the same thing
I added a compiled version of bless for download on the fatdog64 contribute thead:
http://murga-linux.com/puppy/viewtopic. ... 83#1006083
As noted bless renders better than wxhexeditor but is likely heavier weight since it relies on mono. That said I recommend bless much more than wxhexeditor as a hex editor but it isn't as good as glogg if one just wants to view a large text file.
http://murga-linux.com/puppy/viewtopic. ... 83#1006083
As noted bless renders better than wxhexeditor but is likely heavier weight since it relies on mono. That said I recommend bless much more than wxhexeditor as a hex editor but it isn't as good as glogg if one just wants to view a large text file.
I would suggest vim (not vi, which is a link to busybox on most systems). Fatdog64 devx includes vim.
As a viewer: vim -R file (read-only)
As a binary editor: vim -b file
As a stream editor: cat file | vim -
vim (without complicated plugins) is very fast, works in terminal, and has a separate GTK version (gvim, in the Fatdog64 contrib repo).
As a viewer: vim -R file (read-only)
As a binary editor: vim -b file
As a stream editor: cat file | vim -
vim (without complicated plugins) is very fast, works in terminal, and has a separate GTK version (gvim, in the Fatdog64 contrib repo).
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
- Colonel Panic
- Posts: 2171
- Joined: Sat 16 Sep 2006, 11:09
Vim is great I agree, but in its non-GUI form I fear it may be too intimidating for beginners (I really should send in my donation to Bram as I've been using it on and off for nearly 20 years now).step wrote:I would suggest vim (not vi, which is a link to busybox on most systems). Fatdog64 devx includes vim.
As a viewer: vim -R file (read-only)
As a binary editor: vim -b file
As a stream editor: cat file | vim -
vim (without complicated plugins) is very fast, works in terminal, and has a separate GTK version (gvim, in the Fatdog64 contrib repo).
This tutorial tells you how to navigate a file in Vim;
http://vimdoc.sourceforge.net/htmldoc/usr_03.html
Gigabyte M68MT-52P motherboard, AMD Athlon II X4 630, 5.8 GB of DDR3 RAM and a 250 GB Hitachi hard drive running Ubuntu 16.04.6, MX-19.2, Peppermint 10, PCLinuxOS 20.02, LXLE 18.04.3, Pardus 19.2, exGENT 200119, Bionic Pup 8.0 and Xenial CE 7.5 XL.