dano
micro-editor
dano | micro-editor | |
---|---|---|
15 | 227 | |
129 | 23,964 | |
- | - | |
8.2 | 9.4 | |
30 days ago | 4 days ago | |
Rust | Go | |
Mozilla Public License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dano
- Dano is a wrapper for FFmpeg that checksums the internal file streams
-
Using hash to compare files
You should check out my program dano. It has a dupe detection function.
-
Use `dano` to find duplicate media files
dano is a wrapper for ffmpeg that checksums the internal file streams of ffmpeg compatible media files, and stores them in a format which can be used to verify such checksums later. This is handy, because, should you choose to change metadata tags, or change file names, the media checksums should remain the same.
- verify files excluding metadata using ffmpeg
-
Name a program that doesn't get enough love!
dano - a hashdeep/md5tree (but much more) for media files
-
Frustration with Linux'y installs... just venting....
My best advice (from a person who knows only enough to package his own projects) is it depends on the project. For my own Rust projects, I've found a Debian autopackager called cargo-deb for cargo. I convert those deb packages to rpm with alien. I upload both to the repo manually, and have a script which generates what I need and uploads to a PPA.
-
Ubuntu/Debian Users: Something to be thankful for -- a `httm` PPA
The meaty part of the holidays comes a little early this year for Ubuntu/Debian users, as I've prepared a special treat -- a PPA for httm (and dano)!
-
How you protect and back up your music? I have an external drive and I am afraid that one day it will be damaged and I will lose everything
If you use something like ZFS, then you have a system thats watching your entire data path. If you're not paranoid, afraid of other ways your data can be corrupted, bit rot, etc. (again you do you), you might still want to look at a program I wrote awhile ago, dano, and have a system to periodically verify the data on disk.
-
Using `httm` and ZFS to detect file modifications for `dano` (or getting a little sleazy to do a little good)
One thing ZFS doesn't do (and thank goodness it doesn't?), it doesn't detect out-of-band changes to files. If a program has the permissions to modify a file, ZFS happily modifies that file. But, for some files (and for the truly paranoid), we may want to keep additional metadata about file integrity. For instance, FLAC files keep checksums of its music streams. A program I wrote, dano, provides a way to do the same for all FFMPEG compatible media streams.
-
`dano` verifies your FLAC hashes 50% faster than `flac`
Packages and source available for dano at the following link.
micro-editor
- Ask HN: What software sparks joy when using?
- Modeless Vim
-
Essential Command Line Tools for Developers
To see more screenshots of micro, showcasing some of the default color schemes, see here.
-
Go: What We Got Right, What We Got Wrong
Not sure these are really popular, but I cannot resist advertising a few utilities written in Go that I regularly use in my daily workflow:
- gdu: a NCDU clone, much faster on SSD mounts [1]
- duf: a `df` clone with a nicer interface [2]
- massren: a `vidir` clone (simpler to use but with fewer options) [3]
- gotop: a `top` clone [4]
- micro: a nice TUI editor [5]
Building this kind of tools in Go makes sense, as the executables are statically compiled and are thus easy to install on remote servers.
[1]: https://github.com/dundee/gdu
[2]: https://github.com/muesli/duf
[3]: https://github.com/laurent22/massren
[4]: https://github.com/xxxserxxx/gotop
[5]: https://github.com/zyedidia/micro
-
Text Editor: Data Structures
> The worst way to store and manipulate text is to use an array.
Claim made from theoretical considerations, without any actual reference to real-world editors. The popular Micro[1] text editor uses a simple line array[2], and performs fantastically well on real-world editing tasks.
Meanwhile, ropes are so complicated that even high-quality implementations have extremely subtle bugs[3] that can lead to state or content corruption.
Which data structure is "best" is not just a function of its asymptotic performance. Practical considerations are equally important (arguably more so).
[1] https://github.com/zyedidia/micro
[2] https://github.com/zyedidia/micro/blob/master/internal/buffe...
[3] https://github.com/cessen/ropey/pull/67
- A nano like text editor built with pure C
-
A simple guide for configuring sudo and doas
There are two main ways to configure sudo.The first one is using the sudoers file.It is located at /etc/sudoers for Linux,and /usr/local/etc/sudoers for FreeBSD respectively.The paths are different,but the configuration works in the same way. A typical sudoers file looks like this. The sudoers file must be edited with the visudo command,which ensures the config is free of errors.Running this command as the root user will result in opening vi by default.If you want to use a different editor you can set the VISUAL environment varaible to the editor you want. For example,if you want to use micro as the text editor run:
-
what terminal emulator do you use and why?
found that micro has dedicated info page for copy paste
-
Microsoft is exploring adding a command line text editor into Windows, and it wants your feedback
micro: winget install zyedidia.micro
- What is the best basic ass text editor?