Monday, May 19, 2025

Notes on Yazi

 Yazi is good.  Real good.  I used it over ssh to cull a directory on my second system; it worked as I had hoped, except, perhaps, for color theming.

 Knock on Wood.

 Viewing/reviewing

One of the needs that yazi has fulfilled for me is rapid viewing.  I can only imagine that should I ever be able to upgrade my current machines (RAM and CPU, as well as Storage), viewing would be even more friendly, especially for images.  The ability to flip through a directory of images, mark, and move, copy, or delete marked files, has made a huge difference to my workflow.  The only other tool that is useful in this regard is xnviewmp.  I use a fairly simple set of commands; probably if I mastered tabs and other complexities and plugins, yazi would be even more helpful.

 

By the way, the terminal "kitty" has wonderful facilities built in to work well for viewing images.   I prefer the black background and contrasty color scheme to any other.

 Ranger was good enough, until it wasn't.

Copy, Paste and move and Notes on plugins.

 [Cautionary note: I have lost files through carelessness here, and yazi has some gotchas to be navigated around.]

This is pretty much self-explanatory.  I will try to address this topic in detail at some future time.  For now, I'll mention a plugin that has helped speed these processes: 

  • yamb is a bookmarking plugin that works well.  In the absence of a much needed multi-step backup command, this does a good job when sorting through files and moving or copying them to another directory.  I have gotten around the mentioned limitation by defining  bookmarks for the current from directory, and the currently interesting goto directory,  I define a set of book marks to frequently used directories, as well.  This is an easy tool to master.  Like other plugins, issues have been experienced after updating yazi (it is under fairly intense development).  
  • toggle-pane: This helps when viewing both pdfs and images.  It is possible to configure the mazimum size of displayed images (I'm not certain whether this works for pdfs) by putting this code into ~?.config/yazi/yazi.toml:

                       [preview]

                      # Change them to your desired values
                      max_width  = 1800
                      max_height = 1800
  

       Plugins are found on a resources link on yazi's web pages.  Other sites exist with plubins.

 

Filtering

Filtering is a wonderful way to sort.  It has been even more useful to me, because of a filenaming scheme I have adopted.  I stole this idea from Protesilaos's Denote system.  I have not found denote very useful, but the concept of tags at the end of the filename, before the extension has become a useful tool allowing me to sort files more rapidly.  Here is an example.

    Jones--2060--JargonInBiology__taxonomy_nomenclature_zoology.pdf

I have started avoiding underscores in filenames ("_") in favor of using them in tags.  Interestingly, I saw a web page or thread somewhere about tagging styles, and this is one of several.  I used to use a 10 (or so) character at the beginning of lines in a bibliography, where each position had a meaning.  So anything related to crabs would have "c" in the third position (12ctx8urt-Anon-Crabs of the world) would be sorteable by sorting by the third position.  The Unix (GNU/Linux) sort command worked excellently.  

 With filtering  in yazi, one can narrow down a large folder/directory with pdfs about taxonomy: "_taxonom".  Prot has demonstrated the use of regular expressions to sort even more specifically in, I think emacs dired.  To avoid filtering for "_" in filenames, one would theoretically use a regular expression requiring a "__" (double underscore) somewhere before the "_:" single underscore.  This is probably easy.  Filtering is easier, I think.  It may be that emacs would be better, but so far, aside from a couple of learning experiences, Yazi is working well.

Moving around 

In either the getting started or tips section of the yazi main web pages, is a suggestion that makes yazi more useful.  

Inserting this code into .bashrc (and I think .zshrc as well) makes things easy.

 function y() {
    local tmp="$(mktemp -t "yazi-cwd.XXXXXX")" cwd
    yazi "$@" --cwd-file="$tmp"
    if cwd="$(command cat -- "$tmp")" && [ -n "$cwd" ] && [ "$cwd" != "$PWD" ]; then
        builtin cd -- "$cwd"
    fi
    rm -f -- "$tmp"
}

Then, when in a terminal, type "y" to start yazi.  After moving to another directly, quitting with "q" leaves the terminal in this new directory.

 

A Caution or Two 

 Plugins are often not mutually compatible.  I have tried several others, but some collided with these few i do use.  

Some plugins iexplicably use keybindings that are assigned to other functions by default, and it is not always apparently what key bindings may be used.  <F1> may display a help screen, which may be filtered.  Filtering rocks.  Bookmarks rock.

 

2025 May 19

 

 

             

Further notes, after some time with Endeavour

 My initial impression of EndeavourOS/i3wm was a sour one.  Now that I have installed it on two machines, my positive impression of it, this time around, has moderated.  I may uninstall and go the tortuous route, installing Archlinux directly.  Not yet, but perhaps...

I could not do better in expressing my chief complain than another user (anonymous, I fear), who wrote a comment to a thread about i3WM on Endeavour.OS  In effect, this user remarked "It seemed more like one person's favorite custom install than a generally useful one."   Hear hear!!  Another user remarked that a seasoned i3wm user would find the customizations of the EndeavourOS tweak to i3wm, in effect, difficult to use.  


Other users pointed out that during the install an obscure checkbox allows one to skip EndeavourOS (EOS) customizations.  After installation is not a favorable time to learn about this, and it warns me against ever reinstalling this OS.

The OS is slick.  Too slick for i3wm.  Even the login screen is over the top, IMHO.

Another suggestion was to delete the directory ~/.config/i3 completely.  


What I have done is copy over, mostly, my config file from Manjaro.

 

Now I will mention the one thing that EndeavourOS does that works better for me, as I did in my last post: it used Archlinux repos out of the box.  Manjaro has taken pains to filter the repos so that they seem to able to go out of date, as I believe happened to me. 


I can see no need to continue to flog this dead horse.  I will continue to use it until I find time to install something else, probably Arch.  


Monday, May 12, 2025

EndeavourOS GNU/Linux: notes

 I have installed EndeavourOS, i3wm on two machines: a self-built/self-maintained PC, and a Lenovo S1 Yoga.   On both, as of now, it is working well, some 2 weeks in.  Why EndeavourOS?  I'm not sure.  I was experiencing some glitches on my Manjaro systems, and I needed to refresh the Lenovo S1 Yoga i3 installation.  In retrospect, after all of what I list below, it seems to me---though without having anything specific in mind---that Manjaro's i3wm flavor has fallen behind. 

Some key points:

  • EndeavourOS i3wm edition incorporates a number of idosyncratic modifications and customizations.  This was my sense on previous short-lived installs, and it remains so, perhaps to an even greater extent, today.
  • The first thing one notices is i3wm keybindings.  They differ in almost every respect from i3wm defaults, without, AFAICT, any particular reasons.  
  • Installing  a printer reveals what may be a well-kept secret: the default firewall blocks a printer; certain adjustments must be made.  The "install-system-printer" tool, not an obvious feature, makes accomodations to this roadblock;  however, it may not be obvious to one who has been installing a printer by usual methods, such as starting up cups and opening "localhost:631" in a browser.  I, for one, was unaware of the firewall settings, making it necessary to chase down the differences.  Fortunately, I stumbled upon the script.
  • i3wm's configurations file, located at .config/i3, sources a number of scripts in .config/i3/scripts.  
  • The shutdown/resume/etc process found in, for example, Manjaro's i3wm edition, is implemented as a popup menu, via one of these scripts, powermenu, which requires a mouse click to activate.
  • EndeavourOS exhibits a fondness for visual icons.  These are overdone, for example, in the powermenu script, and in the status bar, etc.. To my eye, these icons are distracting.
  • EndeavourOS seems to reflect a trend toward modernization of i3wm, and perhaps other desktops.  
  • Some defaults are welcome; others were troublesome, at least for me. 
  • The installation caused some hiccoughs.  I don't remember them; I had to reinstall three or four times, for at least one of my machines.   
One serious problem I encountered during installation was the step, which I had overlooked, of having to choose between a BIOS and a UEFI installation.  This presented a serious problem.  I have never encountered this in any previous installation of Manjaro or Archlinux.  (I have abandoned direct installation of Archlinux because the learning experience touted by the developers has become a hindrance: after at least 10 installations, I have not learned them to any helpful extent; various versions of this process have presented, overall, significant hindrance to productivity. 

I was able to recover, for the most part, to a very nice OS, by copying over my config file from my previous Manjaro i3wm.  To be fair, this file has evolved over a decade or more, and incorporates useful tweaks.  Like Emacs's .emacs file, these tweaks---indeed the entire experience---remain relevant, without interfering with functioning of EndeavourOS.  Tweaks---mostly inspired by a series of videos from the distant past by Luke Smith, include:
  • A dropdown terminal (using Kitty in my case)
  • A dropdown Emacs instance---extremely useful;
  • A dropdown terminal running R, for calculations
  • A popup calendar: orage, a wonderful calendar, the best IMHO;
  • A popup "ham radio clock," helpful for my calendar work.
  • Two additional specific scratchpads, which I seldom use;
  • Workspace flipping abilities
  • custom bindings of kmag and kde-connect, which I use for microscope work.
 These features make i3wm even more useful.  I also customize other features, in minor ways.
 
Another personal note:  I always install on four partitions,  usually requiring some editing of /etc/fstab:
  1. /
  2. /home
  3. /usr/local
  4. /boot/efi
  5. (and swap; does that count?)
 Using a separate /home parition over the past 15 years or more has helped me to recover when something goes haywire, and it has given me a consistent work and storage setup.  
 
I always use a unique user name; and change the user id to "1004" after installation, by dropping to a superuser virtual terminal before logging in, the first or so time; this renders all user files read+writable, so various work areas, like my "KEEPERS" top level directory, may be copied over instantly.  Group id must be changed likewise, and all files that are not owned by this user:group combination in the current (or other) instance may be harmonized by executing "chown -R newuser:newgroup ~/.
 

A separate /usr/local directory (or folder if one will) enables the ability to carry over programs I have compiled myself, to the new system.   I reinstall texlive using the package "texlive-installer"; this is a wonderful tool.  It is not necessary, but some links may not carry over.  I have been setting up the /usr/local mount by hand in /etc/fstab, because different installers seem to handle the attempt to create it during installation, differently. 
 
Other directories must also be set up by hand, for example:
  • ~/Pictures (a large partition)

For now, I am happy enough.   In case of a need to reinstall, I would probably seek a distro that holds true to i3wm defaults.

 

Obviously, I am a fan of i3.  Endeavour would not be my first choice except that it seems well constructed and efficient.  The GUI enhancements are not excessive, but they are too much for me.

 

UPDATE:  I have followed some random advice to uncheck "opengl flipping" after experiencing serious lags upon resuming from suspend.  We'll see....  So far, no lag, but will try again.  

 Ok, I've tried it with only one application running, and things are fine.  What I had experienced were long delays, mouse unresponsive, when resuming.  Fingers crossed.

 

 

 

 

Tuesday, February 18, 2025

2025: I am still running on Manjaro

My history of distro-hopping between 1993 (or 1994) and early 2025 is worth a story.  The first time I installed GNU/Linux (on my Toshiba Laptop), the choice was between FreeBSD and "Linux."  I downloaded Slackware, through the kindness of the owners of Kuentos Communications on Guam.  I knew nothing of Linux, but after installation, faced with a terminal, I did not know what to do.  What I did was a head-scratcher: I typed "top".  It was a propitious choice: top is a system monitor that I still use in 2025, in it's  modern iteration, as "htop."  Slackware is still alive. 

 I did not install, Yggdrasil, even though it looked.

 At some point, perhaps 1995, I finally abandoned Slackware, for Debian, which was connected with the Free Software Foundation.    I stuck with Debian for a while.  One thing I noticed about Debian, and perhaps other distros further on down the line (Ubuntu) was the impatience of the developers who inhabited the help mailing list.  Instead of a simple answer, one would receive a sharp rebuff because he did not RTFM.  (Read the Fine Manual).  Another problem still persist, and has become even more egretious, IMHO: list lurkers who answer questions with "I don't know." 

 In about 1996, I hopped over to Ubuntu.  This was inspired because it was easier to install than plain Debian; but in fact it was a version of Debian that was easeir to install and maintain.  But Ubuntu was frequently problematical, for me.  Others seemed to be fine with it.  

Next was Knoppix was an interesting side-trip; I installed Cluster-Knoppix on three computers which I built for my classroom at Marianas High School.  With a student, we   actually got a cluster working, at least for a while.  Knoppix, in it's own rite, was easy to install.  It was possibly the first Live CD distribution, and it was simple to install onto a hard drive.

One issue that required constant head banging, was installing printers.  Even until this day, most printer manufacturers do not support GNU/Linux.  There are exceptions.

 Another problem has been incompatibility of software.  This was expected; however, the worst was software---often developed with Government funding---for educational use.  

It has been worth the trouble.

I do not remember when, at some point I started getting in over my head---with Gentoo. With Slackware, I had learned to install Unix software by compiling it from "upstream" source code; this means, the original code.  Debian in particular had painted this upstream code with another layer of patches, and generally made it available as pre-compiled binaries.  This approach was a little uncomfortable for me; I always had hoped for a distro that used upstream source code.  This brought me to Gentoo.  

Computers are tools.  I am interested in them, sure, but as tools.  Tools for functional purposes.  Gentoo's approach was elegant; but frequent updates led to collisions between library versions---especially with KDE's libraries---and routinely to gordion entanglements.  I install a large number of software packages, which leads to a large number of such problems.  The tedium started to bother me: the all night updates, the need to reinstall---often taking days---when things got too complicated. 

This is true: Gentoo had the very best documentation, by far, of any distro.  That was, however, until a fork in the road when developers went through some life changes that caused the documentation system---alas!  the distribution itself---to cease to be accessible to mere mortals like myself.  

Ubuntu was visited a few more times, and Mint Linux.  Neither of these worked for me.  Ubuntu---for reasons I never will understand---often abandoned me at a black screen of death.  Mint was not my cup of tea.

I landed on Arch Linux.   

Arch is touted as a learning experience.  Sure, it's difficult to install, but every user needs to learn the system from the inside out.  After many re-installs---probably often as a consequence of my own incompetence---I realized that I had not learned the lessons, as I had to repeat the same steps over and over again, cluelessly.  Eventually, though, I found Manjaro.

 Manjaro, IMHO, is the best of the Arch derivatives.  Manjaro (along with Arch Linux) will best be treated separately.  Suffice it to say, I have not hopped from Manjaro---save a few short-lived adventures with other Arch based distros---for well over a decade.

 

 


Monday, February 10, 2025

Unix's and GNU/Linux's Unknown Superpowers: ptx, sort, and grep

The Unix operating system is wonderful.  GNU/Linux is wonderful.  Let me make this distinction, before discussing the aforementioned three tools: GNU is Not Unix. This is a story of how capitalism limits the human spirit, in order to extract financial gain.  

 Before writing about the remarkable tools provided by Unix---and now, the GNU computing system (one of the scions of which is GNU/Linux)---one may be forgiven for visiting certain concerns, including the generation of incomprehensible wealth by a few men who now seek to control our lives in ever more of their detail.  I suggest that this wealth was made primarily through marketing, on the backs of the ingenuity of other men, some of whom were out-maneuvered and left behind by certain well known business men.  

It came about, during the early days of computing, long ago: a gifted programmer by the name of Richard Stallman worked at MIT Artificial Intelligence Laboratory (MITAIL), along with other highly capable computer programmers.   Events during that period led to unforeseeable changes, as a behemoth technical-industrial complex grew beyond all imagination, based on deft slight-of-hand and shrewd business moves, as entrepreneurs snatched up computer code, patented and copyrighted it, and concealed it from hapless consumers.  Shrewd manipulations of programmers and code enabled a few men, in less than 50 years, to accumulate over half of the wealth of the financial world.  

This they were able to do by convincing consumers not to share, with the complicity of the legal "intellectual property" infrastructure; to violate the golden rule that many had cherished since childhood.  Make many copies of a useful computer program for a few pennies each, and set prices  arbitrarily high.  The consumer will be so mesmerized by the utility and flashiness of these programs that she will believe you are doing her a favor, selling it so cheap.  Convince governments to sign lucrative contracts.  Update products at speed, and charge for the updates.  Sue public schools when they did not update to newer licenses.  the profits would be almost unlimited.  And, now, change the business model and lease software, so leverage even greater control, and much greater profits. Never do unto others anything without transactional benefits to self.  Above all, do not share a computer program, even though they are useful.  This was a massive wealth grab. 

Tim Wu has written about the  entrepreneurs who built incomprehensible wealth by these same strategies: seize control of the media channels, prevent newcomers by various and nefarious means, and charge arbitrarily high rates for the use of this now valuable commodity:  information.    Radio. Telegraph, Telephone, and Television have been used to manipulate the public, by employing choke points---selective filters---to manipulate elections, gain power, and sell snake oil.  The political landscape has been altered in the interest of gaining more power, prestige, wealth, and control.  It's OK, these persons believe, to lie and deceive.  Today's politicians have gained success by following a model of radical "gas lighting," and in doing so have built empires  of corruption and greed.  

You may know this story. 

 Richard Stallman has been painted under the dark lights of deception as an extremist, even among other adherents to Free Software.  This is how the insidious tactics of industry and politics can influence our opinions to their own benefits.  The Petroleum Industry, in a similar manner, convinces us that global climate change is a hoax, that CO2 is fine.  Our politicians convince us, who are eager to consume their distorted and deceptive messaging, of these things, and many others.  We know they are lying, but the steam engines of their corruption are traveling down the tracks with such unrelenting force and momentum that they seemingly have taken over our own minds and hearts.  

 This is about one little part of the story. 

The MITAIL was at the forefront, in those beginning days of computing.  Richard Stallman was there; he noticed that the software interface of their very expensive printer was inefficient, klunky.  In the hopes of improving this interface, he kindly offered to the company that owned the patents,  to tweak the software and make it work better.  The manufacturer, however, was unwilling to open up the code behind that software, fearing loss of control and profit if it ware revealed.  

This is an important story, but this is not our story today.  Suffice it to say that Richard Stallman decided to do an end-around, in the finest traditions of human cooperation and sharing.  The Unix Operating System, owned by Bell Laboratories (AT&T), was an outstanding work of programming, a thoughtfully produced system of software, an interface of great utility, with numerous subprograms attached to a central kernel, making a whole that by far exceeded the sum of its parts.  But AT& T owned Unix. In the capitalistic world, this was a fantastic money maker.  But the cost of ownership was onerous, making it impossible for the average computer user to purchase.  And as Stallman had already learned, the impediments that proprietary software posed to even the best programmers presented various difficulties---even beyond simple ownership.  The experience with a printer had taught that lesson.  


And what about sharing these wonderful tools?  Stallman recalled an earlier time when the many talented programmers and users at the MITAIL had freely shared programs they had developed.  As a consequence of this open access to the universe of such software programs, even greater programs were spawned from the synergism...  But now many of those programmers had been enticed to leave this world by unimaginably lucrative contracts.  But  these contracts had been concealed within a trojan horse: the non-disclosure agreement.  The code, they promised, they would not share.  And even the end users, who purchased such programs today as Photoshop, Lightroom, games, typing tutors, graphics printing programs....  ad infinitum, are coerced into not sharing the software they purchase.  The industry is serious about this limitation.

So Richard Stallman reached out on the internet to propose a collaboration of programmers to build a new computer system, a free system, that could be "shared without dishonor."  Remember how Unix comprises a set of software units that are hook in to a kernel?  Those units include various commands: copy and move files, for example.  Even typing on a keyboard is handled by tools hooked into the kernel.  The construct, from a plethora of these units, is an Operating System (OS).  Such operating systems as the proprietary MS-DOS, Windows, and MacOS are example of proprietary OSes.  It is forbidden by the proprietors of these OSes to share the programs.  At great expense, these companies have constructed elaborate schemes to make it difficult or (they hope) impossible to share these programs.  

 Do you see where we are going with this?  This massive construct, including now Microsoft, Facebook, Apple, Google, Oracle, Adobe, and others, has used a strategy of concealment, of forcing others to not share, to build huge empires, and horde wealth.  Intimidating the consumer, for example by suing Portland, Oregon's public schools to force purchase of contracts for every copy of windows that had not been updated, as "required" by the manufacturer.  

But GNU is Not Unix.  Richard Stallman recognized Unix as a wonderful model for an OS.  If thousands of programmers all over the world, connected by the Internet,  were to each write one or a small number of   utility programs, mirroring those that perform the functions  of  the Unix programs, while avoiding even any appearance of copying the Unix code, a new operating system could be built up through community action, a citizen-built computing system.  This system was successfully built.  Even a protracted legal challenge by the owners of Unix, SCO, many years later, could not find any copied code in the GNU/Linux operating system.

When I was isolated in Chuuk Lagoon, I had been conducting research that required access to computers.  My family donated a laptop computer, but the Windows OS was clumsy, and, to cut to the chase, could not help me with my project.  An editor that had been sent to me by a linguist at the University of Hawaii was capable, but it was "cripple ware," in a sense, and without the manual---which sold separately for hundreds of dollars--I could not proceed.

 

 The Free Software Foundation (FSF) responded to my request for an editor, sending a version of the Emacs editor ported to Windows, along with 14 disks of Unix tools, also that would run on Windows.  This was just what I needed.  Among these tools were a number of Unix text tools, opening a window into a new world of possibilities.  Very important to me were sort, grep, and ptx.  These, as far as I am concerned, are core Unix (hence Linux) superpowers. 

sort

Windows had a sort utility, but it was extremely limited.  In fact, the more I learned of the tools granted to me by the FSF, the better I understood the fraud that had been perpetrated on the public, corporate world, and governments by Microsoft.  I can liken the difference between the facilities provided by Unix (and later by Linux and FreeBSD) is comparable to the difference between a set of cheap carpenter's tools, and professional quality tools.  GNU sort is the Cadillac of sort programs, the Rolls.  

Later, on Guam, I was able to download a copy of the new Linux OS on Guam.  It was then that I discovered liberation.  From that day, in the early 1990s, until today, in 2025, I never never felt comfortable on a Windows computer.  At that time, one of the biggest differences was that Linux was capable of doing true multitasking, while Windows only could do one operation at a time.  With GNU/Linux I could type a letter while printing a different document, and running another process in the background.  Another difference was the Linux did not crash.  Let me repeat, it never crashed or locked up.  Windows regularly did so.  

grep
 
 I will not explain grep.  Today, in the 2020s, one can run grep on Windows machines.  Suffice to say that grep is a tool that enables searching through a set of files for a search term, and printing to the screen a list of matches. With pipes (signified by the character "|", one can direct the output of grep to another program, like sort.  Then, from sort, one may direct its output to less, a better file browsing tool than Unix's more, a tool that pages through a file.  To do this one would type:
 
    $ grep <filename.txt> | sort | less

 

ptx

 My need was specialized, as I was dealing with lexical text, lists of animal names.  To weed through these, I found ptx was incredible.  Ptx means "permutated index."  What follows is a small segment of output from a search of a text file about flowers and seasons of fishing. 


  /Luma, altitude 100-125 meters,   flower, August 4, 1921, Garber no./
      /\section{Burrows: a different   flower, and palolo.\hfill{}\textsc/
     specifically, he does mention a   flower.
     with certain things. There is a    flower called bust ginger;/    /time
      \textit{Erythrina\/} sp. as an      indicator species.            /about
        /constellation as a seasonal     indicator, he refers to this/
   a resident of Wonipw,/       This    indicator would only be useful to
   the/    /solar alignment as a key   indicator of the   emergence of
      /\hfill{}\textsc{whale:season:    indicator}} \label{sec:org5e260c7}/
     /tree fruits are ripe, it is an        indicator that whales are running/
Samoa/    /was used as a seasonal  indicator on some islands (e.g.,
  /2015, Trees of Yap:  sometimes   indicator of seasons} \label{sec:/
   . \textbf{Sometimes used as an   indicator of season.}       /flowers
   a resident of Wonipw,/       This   indicator would only be useful to
    /variegata\/} flowers in the dry   season, and has been mentioned (/
      and that it flowers during dry   season.       /of year of flowering,
      /these two periods the iéboua   season; the \%\%    season of the/
       /the iéboua season; the \%\%   season of the sun or heat iéboua-/
    /or heat iéboua-délat, and the   season of cold iéboua-tsiam.


tldr

 

Tldr (too long didn't read) is a modern innovation that summarizes the man page for a command.  In Unix, it was specified that who ever wrote a program must provide a "man": page, a manual to its use and options.  Here is output from tldr:
 
$ tldr ptx

  Generate a permuted index of words from text files.
  More information: <https://www.gnu.org/software/coreutils/manual/html_node/ptx-invocation.html>.

  Generate a permuted index where the first field of each line is an index reference:

      ptx --references path/to/file

  Generate a permuted index with automatically generated index references:

      ptx --auto-reference path/to/file

  Generate a permuted index with a fixed width:

      ptx --width=width_in_columns path/to/file

  Generate a permuted index with a list of filtered words:

      ptx --only-file=path/to/filter path/to/file

  Generate a permuted index with SYSV-style behaviors:

      ptx --traditional path/to/file 

Saturday, October 12, 2024

The Free Software Foundation (FSF) is a beacon

I just stumbled upon a statement on the website of the FSF (fsf.org) about the appointment of three new board members of the organisation. I am impressed. The FSF has been on my radar for many years, as I have followed developments in the Free Software world, and used Free Software for my own work. I have been a devotée of free software for over 40 years, as a user. These people at the FSF, as well as the Electronic Frontier Foundation, and GNU: what's not to like? Who is more committed to the concept of free software, free information. freedom from repressive copyrights and patents? Fantastic! The FSF!

Friday, October 4, 2024

VIPSDISP: A quick viewer for jp2 files and for large files in general.

 https://forum.image.sc/t/new-version-of-vipsdisp-a-free-open-source-linux-image-viewer-for-very-large-images/70979

 

Seemed to work fine.  On Manjaro GNU/Linux I had to install a library: openslide.  After doing this, this program started fine.  

 

  

Wednesday, August 14, 2024

Some grousing: I've been experiencing loss of files and directories

I started working on a directory heavily, to aggregate and organize projects into folders, containing various files, mainly PDFs, images, and random other files, including drafts and "sweeps" related to some of the projects. I have some duplicates, for some of the projects; but with all of the work I've put in over the past few weeks, many files have been lost forever. It is my intention to document here any information relevant to this and other recent glitches or losses of data. I am convinced that MacOS is a scourge. I dropped around 1500.00 on a MacBook Pro, M2, 14", earlier this year. I have long avoided Macs; it was my hoep that I would be able to gain some advantages to my work. But I have lost,in aggregate, probably jmore than I have gained. Problems begin to crop up in regard to copying or syncing directory trees between the mac and the Linux box. - A suite of unresolved problems around the case-insensitive file system of the MacOS. - Dropbox sync issues. This has become a serious problem. I think either I have to completely quit MacOS or figure out a way to convert my data all to a filesystem that is case-sensitive, on the Mac. A plethora of small, hidden files now pollute my directories. Since I have lost files on the Linux Desktop, one obvious way to re-connect with many, or some, of those files has been to tar up an entire directory and copy it via ssh to my desktop. Thi does work, but this is where I introduced a massive number of these invisible files onto the GNU/Linux system. Apple's amazing Finder application is one of the culprits, if not the main one. These tiny files, according to one source in an online forum in which a problem, similar to mine, was discussed stated that these files cause directories to be unseen on other operating systems, possibly Windows. I have no way, yet, of finding out whether this has happened to my system; and, anyway, I have reconstructed some of the folders (directories) on my Linux desktop, which means I have commited mayhem on the filesystem as it existed previous to the apparent deletion of important directories. I have entertained the possibility that my incompetence has conspired with a new console based file manager, yazi, that i have come to depend on as I sorted---and contiue to sort---files into topical higher level folders/directories. Fumble fingers. GUI file managers like nautilus have given me fits in the past. Getting better.

Wednesday, July 3, 2024

Yazi: a swiss-army utility, for multiple platforms

 I have been using Manjaro for years, now.  Every so often I contemplate installing Arch, which I like, which is not polluted by Manjaro-specific tweaks; but (1) in spite of assurances, it is problematic to install; and (2) none of the other Arch-based distributions have worked well for me.  

Today I want to mention and recommend Yazi, a text/terminal-based "file manager," similar to ranger and a few clones of ranger.  Yazi is, in most respects, the best of the breed.  Yazi, with a few tweaks and some steep uphill learning, made short work of  culling some 150GB of images.  No other tool has been as efficient.   For me.

The home page for Yazi may be found here.

Configuration

Here is where I mention the steep learning curve.  The usage of this tool was not immediately apparent to me.  This is probably on me; eventually, I found the keybindings in the Quick Start page on Yazi's home page.  Not all of the key strokes were either easily understood, or found.  On my MacBook, the color of my terminal interfered with those of Yazi, so I had to read further, and learn to install a theme; the concept and terminology of themes in Yazi were not intuitive.  For me.  Once I figured out how, it was possible to install a theme in the configuration file; various config files are located at ~/.config/yazi.  

 Previewing images

I was able to view images as soon as I had installed yazi on both the macbook and my linux desktop.  But the image was a little small.  I found a couple of things that helped: I learned I could edit the configuration file that determined the maximum image width; after that, the system ran a triffle slower, but I could see the images.  A plugin called "max-preview" enabled expanding the preview even further, in some cases.  I won't explain.  More information is available on the image-preview page of Yazi's home page.

Previewing works nicely on the kitty terminal emulator.  I like kitty, because, out of the box, it is fast, and has a stark black background and intense coloration of text. 


 Bookmarks

Ranger allows definition of keybindings in a more intuitive way (to me) that enabled me to define keystrokes to jump to certain folders/directories that I used frequently.  I just learned to three bookmarking plugins for Yazi that enable something similar, and at least good enough.  bookmarks-persistent, and bookmarks

More information on plugins can be found here.

After all that

 A rabbit hole was involved.  But along the way I learned about several other tools that, amazingly, integrate seamlessly (sort of) with Yazi: fzf, zoxide, ripgrep, fd and others.  This is a remarkably polished tool, for a package that has been undergoing rapid and apparently continuous development.  


I recommend installing the development version, which is the default version of yazi in the Arch ecosystem's AUR repository.  This enables some of the more advanced tools.


Fortunately , ranger, a tool I have used for years to browse and sort files and directories, does not work anymore---at least easily---for previewing images and PDFs.  In desperation I reached out to Mr. Google, and discovered a few others.  Nnn is unworkable.  I has never worked out of the box, which was a show stopper for me.  Some others exist.  Yazi appeared out of the mists, and answered my call....  

For now, links on the website of Yazi---a site that is well laid out---point to more information about plugins and other vagaries. 


 

Tuesday, April 4, 2023

Thoughts about Manjaro, Endeavour, and Gentoo: Recent Dives into the rabbit holes

I have tried Endeavour Linux in the past; something always feels wrong about it.  It has some good points, though.  When I saw it overtook Manjaro, on Distrowatch, my curiosity got the better of me, so I installed it. 

I still like i3 better than other Desktop Managers (KDE is interesting, but slower, for me).  So I reached for the i3 install.
 
Once again, I am disappointed.  Mostly, it's because of the difficulty I had trying to use Endeavour's idiosyncratic customized i3 setup.

 

Pros

  • It seemed faster (maybe my older Manjaro is tangled up in knots?)
  •  My Manjaro is well worn, feels good, but there are many little issues.  Endeavour felt really speedy.
  •  Quick to boot.
  •  

 Cons 

  • i3 is intractable to me.  It seemed even more difficult than the last time. 
  • Installing the regular config file did not work for me
  •  I do not enjoy the wallpaper
  • Ranger is not installed


On the whole, Endeavour was overwritten in one day with Manjaro.  Manjaro is easier to install, and the setup is familiar.   This is regrettable, because I really want an easy-to-install Arch Linux, with Arch repos, without the manjaro overwatch.  



Tried to install Gentoo recently


About 15 years ago, Gentoo was my favorite distro.  I did not like that updating required more than a day, in my aging (but not horribly ancient) hardware.  Maybe it's time to try again?   


Distrowatch's recently featured review of the Gentoo LiveCD received the highest KUDOs of any I have recently read.  So shouldn't I try it?  

The Live CD is nice.  So I tried to install from the Live CD.  There is no Calamares-equivalent installer.  I followed all the steps.  The Boot Manager did not work.  


So I gave up.  I have work to do.  I cannot spend days installing a new OS.  My machine might be up to Gentoo, but I'd have to rein in my penchant to update every few days.   


I never got to find out whether KDE libraries are still a gordian knot on recent Gentoo.  Also, it's a huge learning curve.  Maybe I'll try one of the easy-to-install  Gentoo shortcut distros, but my patience would be certain to be tested.  There are too many steps for everything.  

I might try again.  Maybe on a clean machine.  I want to try Apple Hardware.  

 

Why not Apple M1 or M2?

 The need for speed has me looking at MacBooks and Mac Minis.  


The biggest need for me is an easier to use search function.  The virtual folder feature is so clean and cool, it might be just what I need.  Or maybe I'm fooling myself.

 

Arch and Manjaro

Manjaro is easy to install.  It is my go to system recovery distro.  Let me explain: The System Rescue CDs leave me at the lurch: I still have to dig around, and I don't do well at that.  I'm what might be called a High-Skilled Linux User Without Computer Skills. I can run a system, but the finer points of system tweaking---involving programming---are a massive challenge.  

I have work to do.  GNU/Linux is my biggest ally, but I don't have time or inclination to spend more time, for example to learn to install Arch every few months.  Arch's supporters say that the Arch installation process is a learning tool.  I've learned it too many times already.  Arch is easier than Gentoo.  Gentoo is too much power; more than I can handle, and I cannot keep it on the road.  Arch is the next step toward independence, but every time, I have ended up stepping on my toes, tripping myeself up, and having to re-install.  Because it's easier to install (esp. with Manjaro) than to dive in to the problems.  Even using the greatest help system: Google and the multitudes of users.  I am so dependent on these folk.  How can I repay it forward?  


:-)

Tuesday, October 12, 2021

Richard Stallman Leaves FSF Again

From DistroWatch.com

John Sulivan, the executive director of the Free software Foundation (FSF), has announced that Richard M. Stallman has resigned his position as president of the FSF. Stallman is best known for his work in creating the free software movement and starting the GNU project, which develops free software that is used by nearly all Linux distributions. Stallman's hard stance on software licensing, along with his controversial views on some social issues and brash communication style, have often made him a divisive figure in the free and open source software communities. This has occasionally led to people petitioning the FSF over the years, asking Stallman to step down.

The most recent controversy around Stallman gained more media attention than usual and resulted in several FSF members threatening to cancel their memberships. Members of the GNOME team announced their intention to cut ties with the FSF and GNU if Stallman did not leave his position. The Free Software Conservancy also placed a similar call for Stallman to step down, stating: "When considered with other reprehensible comments he has published over the years, these incidents form a pattern of behavior that is incompatible with the goals of the free software movement. We call for Stallman to step down from positions of leadership in our movement.". Stallman has also resigned his position at MIT, citing "a series of misunderstandings and mischaracterizations" as the reason for his departure. 

 I have no idea why.  Stallman deserves a good deal more respect than he has gotten.  Over the years, I have been sickened by comments I have seen on various mailing lists and forums.  Many of them comprise little more than offhand name calling.  No question, Richard Stallman's ideas are radical, when taken against the background of a society which is consumer centered and oriented around proprietary commercialism.  

 The best defense of Stallman is to point to the GNU Manifesto.

https://www.gnu.org/gnu/manifesto.en.html 



 

 

 

Notes on Yazi

 Yazi is good.  Real good.  I used it over ssh to cull a directory on my second system; it worked as I had hoped, except, perhaps, for color...