|
|||
Last edited by jmccue; 21st May 2019 at 10:12 PM. Reason: grammer |
|
|||
I use the ee text editor. It comes standard with FreeBSD. I know you need to installl it as a package or from the ports tree, so that ED Mastery book suggested maybe a better place to start, unless you need to use some GNU/Linux distro that doesn't have it installed by default anymore. I wish the OpenBSD communal packages came with the more advanced text editor based on ee, ie. aee or I think its xae for GUI interfaces, (its a long time since I have used FreeBSD).
As far as doas.conf is concerned, the Author inside the man page is Ted Unagast (have I spelled his name correctly?). Anyway, search for his doas pamphlet mastery webpage with Chromium, it doesn't seem to work with other web browsers, get security certificate errors with Firefox and Lynx I think. But his document is not too long but covers the essentials. Its getting a bit old, so some of the contents may need updating - ie. the OP that replied to you said you might have found a bug. Anyway, Take Care and Happy Reading/Experimenting BraveHeart |
|
|||
Quote:
|
|
|||
Quote:
You should use visudo to edit the sudoers file, not plain vi. Last edited by johnR; 15th June 2019 at 12:13 PM. |
|
||||
vim is pretty similar to vi, and is also the default git editor when commiting...
The command Code:
$ git commit
__________________
ThinkPad W500 P8700 6GB HD3650 - faultry ThinkStation P700 2x2620v3 32GB 1050ti 3xSSD 1xHDD |
|
||||
I use ed(1) for specific tasks only. I find it particularly useful for adding new line characters to markup languages such as html or xml. And I use it in situations where no other editor is available. And sometimes in scripts.
But my use excludes regular expressions. Even though there's a large chapter on the use of them in Ed Mastery, and I've gone through the exercises. Several times. I hate regular expressions. For me, that way lies madness. |
|
|||
My 2 cents..........
"ed" of course has its roots based in the development of the Unix OS. Back in the day (mid to late 80's and early 90's) it was the only way to edit what you might consider .conf or batch files on certain IBM (Tm) mainframes as used in the Nuclear Power Plant Simulation Industry. Following a short learning curve (being a paid consultant ) I found "ed" in this particular usage an exceptional well suited tool. Since simulation involves the monitoring, calculation, display of many variables, "ed" facilitated exact methods to alter these files to inject failure of various degree affecting simulation. As stated earlier by a previous poster it allows mental concentration on a line by line basis allowing one to focus on the technical requirements of that line. Since "ed" was the only "line editor" provided on the mainframe it was the "only" game in town. Would I have preferred another editor for this purpose?, given the technology at the time probably not. And of course in the end it didn't matter as it was the only tool provided. Today I have greatly reduced needs for editing files. Therefore I use nano daily for .conf files and geany when fooling around with "freebasic" . Since some of you have experienced problems with .conf file editing using nano I scrutinize those files closer when using nano or if I experience problems can manage them using vi or ed. In the end what editor or processor you choose is normally driven by convenience and suitability and of course personal choice. Last edited by frcc; 24th June 2019 at 09:19 PM. Reason: clarify and correct |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Doas.conf question | staus | OpenBSD General | 6 | 8th November 2018 03:07 PM |
Restrict doas.conf to syspatch only | bsd007 | OpenBSD Security | 19 | 19th October 2018 01:05 AM |
DOAS(1) rules | jjstorm | OpenBSD General | 8 | 11th April 2016 08:09 PM |
Doas has logging? | cpaulette | OpenBSD General | 1 | 13th March 2016 10:24 AM |
doas package | Peter_APIIT | OpenBSD General | 2 | 1st November 2015 07:45 AM |