A brand new slide deck I created (as of this writing) for a presentation I did at my local UG this past week in a style introducing openSUSE to a brand new User …
Keep in mind that I don’t usually put a lot of content into my slides, they’re intended only to hint, and provide the basis for extemporaneous discussion
The other is my personal openSUSE Wiki…
It’s generally a collection of things I’ve encountered over the years…
It started as a collection of notes I kept for myself but then I thought not only would things be easier to find in a Wiki, those notes could be of interest to others as well.
Like every other Wiki, inspect the history of each article to know how current the info is… I don’t spend a lot of time maintaining the articles and if the article is very old, it might be obsolete although I tend to try to create each article in a way to minimize obsolescence.
If you have any questions or want to correct anything you see…
You can PM me
You can modify any of my Wiki, I won’t mind and actually would encourage anyone to change anything they think should be changed. No worry, if I want to undo your changes, I can do so with a simple click
You can create a Forum post asking your question
And, of course the Technical Help Forums are a wealth of knowledge about practically anything you can think of. Whatever question you might have about openSUSE, unless it’s something specific to a new release it’s likely someone has asked that very question before and someone has answered it… Perhaps several times in different ways.
Although I knew most things in the slide, i did find some new and useful things for example the systemtlc command.
I also really like your wiki, scripts and system level are already on the list and since i need a win vm I will take a closer look on docker and the general virtualization section.
I’d also recommend learning as much as you can about bash. One can be a
Linux user without being a Bash user (or guru), but if you want to master
a platform you should speak its language, and the primary language of
Linux is Bash. Trainings online are readily available, but if nothing
else check out The Linux Documentation Project (TLDP) which hosts the
Advanced Bash Scripting guide:
Possibly, “nano” makes use of the “Meta” key and, it is more simple …
I must admit that, “Vi” and “Vim” force quite a lot of finger / brain exercise despite, most commands being a single keystroke – and, yes, the multiple input modes are at first contact complicated …
On the other hand, for older people, such as myself, it helps the fight against dementia, Alzheimer’s and finger rheumatism … >:)
I personally invoke a mix of vim and GUI editor since I have no over-riding preference for either and am willing to use the best tool for the job…
I’ve stopped arguing in the Applications forum about the supposed inability to launch GUI apps from the command line, and if I’m already working in a windowed console might sometimes invoke a GUI text editor from the console as follows…
On Fri, 20 Jul 2018 21:56:03 +0000, Fraser Bell wrote:
> ab;2874410 Wrote:
>> Bleh… underscores are abominable and hyphens should be used instead
>> for better readability.
> Hyphens are for hyphenating, underscores make for better nobreak
>> Religious war started.
> … former Journalist/Editor is now Engaged.>:)
No need to war – I have an extremely large down filled pillow which absorbs and disables all projectiles directed at me … >:) For persistent “warriors” I also have a private black hole which simply causes the things to disappear …
[HR][/HR]According to my (old) copy of the Chicago Manual of Style (fourteenth edition), underlining used to be used by editors to indicate that, the compositor shall set that part of the copy in italic. Following this practice, documents written with typewriters used “underscore” to indicate words to be set as italic …
The gentle art of computing uses underscores as word separators. Occasionally one refers to “snake_case”, which dates back the late 1960’s when the language “B” (a derivative of BCPL) was being defined by Ken Thompson and Dennis Ritchie; the language “B” became the basis of the language “C” which continued the use of “snake_case” – see the book written by Brian Kernighan and Dennis Ritchie …
The alternative is to use “CamelCase” (or, “camelCase”) which was first appeared in a 1954 conference proceedings; a later “first usage” was presented in a 1965 paper. The programming languages “Lisp” (1958) and “COBOL” (1959) allowed a hyphen to delimit the words of compound identifiers. See also, “Hungarian notation” …
Any of the newspapers I worked at, we Editors used notations by circling the word or phrase with our red pen and adding the notation such as:
Times ulit --
for upper&lower case italics,
for Bold Face Upper and Lower,
and would prefix headings with things like:
Futura 36bful - *Content of the Headline*
for 36 point Futura Bold-Face Upper and Lower, and subheadings with
for 14-point Bold-Face Caps.
… and so on.
In typed copy, usually the reporters did not add markup, this was usually done by the Editors using the methods above.
However, senior reporters and columnists were allowed some markup, in which case they would preface italics with <ital> and after with </ital> if doing so as they type. But, they rarely did this. Usually, they would use the above-mentioned methods for any markup they did.
All typed copy was double-spaced to accommodate such markup, as well as edits.
Now that I have gone way off topic, I will quit.
Uh, lemme see: Yes. When I am creating a Linux Study Guide, I at first use these conventions.
It is best to start knowing how to save the shell history from the beginning to avoid asking yourself “what commands did i ran” to do this or that and so on.
Write some HOWTO’s or a FAQ on things that you have done and some TODO/TOFIX list.
Run your own wiki, there is one in the openSUSE repos or when you got to know vim you can play with the vimwiki
Learn how to use a version control system for writing program/scripts.