title: "Testing out HTML Export from Zettlr" tags:

• Zettlr
• Markdown date: 2022-11-07 11:34:33 -07:00 category: Test Pages

Test 1

Test 2

Test 3

Test 4

<span class="hljs-function"><span class="hljs-title">Alert</span><span class="hljs-params">( <span class="hljs-string">"this is a test"</span> )</span></span>

this is a test

• [ ] This is a test
• [x] this is also a test
• this is another test
  • and another
• and 1 more
  1. maybe 2 more? another example test

Tracing BundledModulesPath parameter

[#]

- (on the Start-EditorServices cmdlet)

  This is an attempt at comprehensively tracing the BundledModulesPath parameter. In this log, all uses of the BundledModulesPath parameter will be documented. This will support my unofficial documentation on the Start-EditorServices cmdlet

Unofficial Documentation:

[#]

[syntax section] - (syntax/usage)

[-BundledModulesPath
  < string, not null or empty >]

PSES/module/PSES/Start-EditorServices.ps1:

[#]

[line 44] - (cmdlet-script powershell param block)

[ValidateNotNullOrEmpty()]
[string]
  $BundledModulesPath

[#]

[line 116] - (cmdlet-script C# cmdlet call)

Import-Module -Name "$PSScriptRoot/PowerShellEditorServices.psd1"
Start-EditorServices @PSBoundParameters

PSES/module/PSES/PowerShellEditorServices.psd1:

[#]

[line 11] - (module manifest - root module field)

# Script module or binary module file associated with this manifest.
RootModule = if ($PSEdition -eq 'Core')
    { 'bin/Core/Microsoft.PowerShell.EditorServices.Hosting.dll' }
    else
    { 'bin/Desktop/Microsoft.PowerShell.EditorServices.Hosting.dll' }

- I believe this is a call to the Microsoft.PowerShell.EditorServices.Hosting namespace - still uncertain about this.

PSES/src/PSES.Hosting/Commands/StartEditorServicesCommand.cs:

[#]

[line 24] - (cmdlet definition)

/// <summary>
/// The Start-EditorServices command, the conventional entrypoint for PowerShell Editor Services.
/// </summary>
...
[Cmdlet(
  VerbsLifecycle.Start, "EditorServices",
  DefaultParameterSetName = "NamedPipe"
)]
public sealed class StartEditorServicesCommand : PSCmdlet
{ ... }

Proof:

After discovering that most Linux File Systems and NTFS both support almost any character in a directory name, I've started playing with how I want to setup my developer environments.

I want a system that is easy to access, reproduceable on any system I would use, and follows a standard file hierarchy. I also want the name not to be locked down to just source code (like dev, build, src, etc, repo), but project-oriented files in general (like image-editing, project management files, etc)

To make access easy, any developer/project root directory will be named "#". My reasoning for choosing this symbol is simply: 

• The hash symbol is used just about everywhere in the developer's world from hyperlinks to a header on a blogpage to shebangs in Linux files,
• and that "cd \#" or "cd ~\#" is short and easy to typeout in a console
• "cd \#" works on windows

In directories with duplicates (or on platforms that don't support this symbol), you can choose from any number of names to replace it (projects, hash, hashtag, tag, #tag, #project, sharp, pound, etc)

I may change this in the future. Hopefully, it doesn't break anything. Ha Ha

As for the structure within the directory, I try to replicate the linux/unix standard for naming directories as closely as possible. The original standard used on Linux can be found at:

https://www.pathname.com/fhs/

Currently working towards getting my CompTIA Net+ Certification.

Read up to Chapter 7 of Mike Meyer's Net+ (N10-008) book. Reviewed up to halfway through Chapter 4. Stuck trying to wrap my head around STP lol

This is just a hello world page to see what I can do with Hackaday.io pages. Ignore me :)