Version control can be a good idea if users learn to use it. I found rcs to be the simplest of these systems to learn and use. On Mon, 29 Nov 2021, Linux for blind general discussion wrote: > Tim here. I like putting my configuration files in version control, > whether git, subversion, or even just old-school RCS. That way I > have a complete history of changes, can undo all sorts of changes, > compare various versions, etc. It really helps track down > when/why/where something broke. > > -tim > > > > > On November 29, 2021, Linux for blind general discussion wrote: > > Before editing a configuration file, make a copy of it to another > > file, that way if you do a configuration change you don't like you > > can back out and same goes with any mistakes. If you like your > > changed configuration file, then maybe delete your backup. > > > > > > On Mon, 29 Nov 2021, Linux for blind general discussion wrote: > > > > > Thanks a bundle for all of you folks. I did not know how much of > > > a discussion my innocent and naive question would generate. I > > > learned a lot from your answers. Although I have never messed > > > with configuration files since the days of the autoexec.bat in > > > the days of dos, I think I have enough courage to play with > > > changing some configuration settings using some of the editors > > > you suggested. > > > > > > I launched few of them both in the desktop and in the terminal > > > and I found geany and nano to be easy. I did not find Micro, I > > > guess it is not preinstalled on slint. > > > > > > I know that my editing needs would be very basic. > > > > > > Cheers, > > > > > > Ibrahim > > > > > > On 11/29/21 5:33 PM, Linux for blind general discussion wrote: > > > > There is teachjove and jove is jonathan's own version of emacs > > > > and teachjove can be run without running jove or emacs > > > > directly. This can be done from the terminal for any willing > > > > to learn. I suppose emacs could be configured in the same way > > > > but haven't tried that yet. It probably would need a small > > > > script. > > > > > > > > > > > > On Mon, 29 Nov 2021, Linux for blind general discussion wrote: > > > > > > > >> I actually have a computer science degree and still find both > > > >> emacs and vi to be riddles, wrapped in mysteries, inside > > > >> enigmas and I should probably figure out a way to add puzzle, > > > >> conundrum, and a few other synonyms to that Matryoshka doll of > > > >> an idiom. > > > >> > > > >> I don't doubt the claims they are powerful bits of kit once > > > >> mastered, but they certainly for the faint of heart and not a > > > >> good choice if you just want to edit the occasional config > > > >> file. > > > >> > > > >> I personally use Nano, and it lets you just enter nano to open > > > >> a blank file you can just start typing in or nano > > > >> path/to/filename.ext to open an existing file, but it does > > > >> have some commands that might throw people coming from a > > > >> grapphical editor or word processor for a loop(e.g. save is > > > >> ctrl+o, not ctrl+s, quit is ctrl+x, not ctrl+q) and has cut > > > >> and paste that is line based instead of selection based(e.g. > > > >> ctrl+k cuts the current line in its entirety, repeating ctrl+k > > > >> without otheer input continues adding lines to the cut buffer, > > > >> ctrl+u uncuts evereything in the cut buffer, copying is > > > >> accomplished by uncutting where youo cut, then uncutting again > > > >> where you want the copy). Also, pressing ctrl+g will bring up > > > >> nano's full command list, while the most commond commandsare > > > >> printed on the bottom two lines of the screen. > > > >> > > > >> For simpler console text editors, there's also Micro, which is > > > >> similar to Pico/nano, but has key bindings more in line with > > > >> the majority of graphical editors. > > > >> > > > >> _______________________________________________ > > > >> Blinux-list mailing list > > > >> Blinux-list@xxxxxxxxxx > > > >> https://listman.redhat.com/mailman/listinfo/blinux-list > > > >> > > > >> > > > > _______________________________________________ > > > > Blinux-list mailing list > > > > Blinux-list@xxxxxxxxxx > > > > https://listman.redhat.com/mailman/listinfo/blinux-list > > > > > > > > > > _______________________________________________ > > > Blinux-list mailing list > > > Blinux-list@xxxxxxxxxx > > > https://listman.redhat.com/mailman/listinfo/blinux-list > > > > > > > > > > > > > _______________________________________________ > > Blinux-list mailing list > > Blinux-list@xxxxxxxxxx > > https://listman.redhat.com/mailman/listinfo/blinux-list > > > > _______________________________________________ > Blinux-list mailing list > Blinux-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/blinux-list > > _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/blinux-list