-Coding Style Guide
+Coding
+Style Guide
@@ -277,7 +148,7 @@ avoid escapes, really)
quoted_string = (
'"You miss 100 % o f the shots you don' t take - Wayne Gretsky"'
' - Michael Scott'
-)
+ )
That brings me to my next point.
2) Long strings belong in
parentheses
diff --git a/tutorials/pc_gaming/common-gfx-card-installation-woes.html b/tutorials/pc_gaming/common-gfx-card-installation-woes.html
index 286b4ab..c3731b2 100644
--- a/tutorials/pc_gaming/common-gfx-card-installation-woes.html
+++ b/tutorials/pc_gaming/common-gfx-card-installation-woes.html
@@ -6,154 +6,24 @@
common-gfx-card-installation-woes
+
Contents
I recently upgraded by PC from an Nvidia 1050 Ti card to a new 3060
diff --git a/tutorials/splunk/i-found-out-splunk-macros-are-awesome.html b/tutorials/splunk/i-found-out-splunk-macros-are-awesome.html
index 10e8567..d1ea507 100644
--- a/tutorials/splunk/i-found-out-splunk-macros-are-awesome.html
+++ b/tutorials/splunk/i-found-out-splunk-macros-are-awesome.html
@@ -6,154 +6,23 @@
i-found-out-splunk-macros-are-awesome
+
Macros are for more than just canned searches.
@@ -173,13 +42,14 @@ time. That report might look something like this:
I can easily review that lookup like so:
| inputlookup vpn_users.csv
My boss might be happy that I'm keeping an eye on things, but what's
-the historical picture? How do I know what's a red flag and what isn't?
-What I might do is combine all of the days reports into one each day,
-and then compare each today. But in the original report logic, this gets
-overwritten every 12 hours. You could just append forever, but then
-you're not looking at just twelve hours, unless you add a time
-constraint to your search. How do I get to a daily report without
-interrupting the reports already running?
+the historical picture? How do I know what's a red flag and what
+isn't?
+What I might do is combine all of the days' reports into one each
+day, and then compare each one to today's. But in the original report
+logic, this gets overwritten every 12 hours. You could just append
+forever, but then you're not looking at just twelve hours, unless you
+add a time constraint to your search. How do I get to a daily report
+without interrupting the reports already running?
One way to do it is to create a second combined report unique to that
day, for example 'vpn_users-2022_11_17.csv'. The way you insert that
text is with a macro, defined for the current date. For this particular
diff --git a/tutorials/tor/how-to-host-a-tor-hidden-service.html b/tutorials/tor/how-to-host-a-tor-hidden-service.html
index de381e5..b2a6ed7 100644
--- a/tutorials/tor/how-to-host-a-tor-hidden-service.html
+++ b/tutorials/tor/how-to-host-a-tor-hidden-service.html
@@ -6,164 +6,35 @@
how-to-host-a-tor-hidden-service
+
Contents
diff --git a/tutorials/vim/how-to-fix-neovim-nerdtree-rendering-issue.html b/tutorials/vim/how-to-fix-neovim-nerdtree-rendering-issue.html
index a3ab430..c90f1c2 100644
--- a/tutorials/vim/how-to-fix-neovim-nerdtree-rendering-issue.html
+++ b/tutorials/vim/how-to-fix-neovim-nerdtree-rendering-issue.html
@@ -6,154 +6,24 @@
how-to-fix-neovim-nerdtree-rendering-issue
+
Contents
I really like neovim since COC is integrated with
diff --git a/tutorials/www/how-to-make-this-site.html b/tutorials/www/how-to-make-this-site.html
index f3d674d..2a631e4 100644
--- a/tutorials/www/how-to-make-this-site.html
+++ b/tutorials/www/how-to-make-this-site.html
@@ -6,188 +6,60 @@
how-to-make-this-site
+
Contents
diff --git a/tutorials/www/quick-intro-html-css.html b/tutorials/www/quick-intro-html-css.html
index 4cdb434..4248bd9 100644
--- a/tutorials/www/quick-intro-html-css.html
+++ b/tutorials/www/quick-intro-html-css.html
@@ -6,190 +6,65 @@
quick-intro-html-css
+
Contents
--
cgit v1.2.3