## Where communities thrive

• Join over 1.5M+ people
• Join over 100K+ communities
• Free without limits
##### Activity
• Jan 26 08:19

RickStrahl on main

Update Changelog.md (compare)

• Jan 26 06:48
jbridgy opened #1002
• Jan 25 23:56
joemclain commented #1000
• Jan 25 23:07
RickStrahl commented #1000
• Jan 25 23:04
RickStrahl commented #1000
• Jan 25 22:57
joemclain commented #1000
• Jan 25 22:21
joemclain commented #1000
• Jan 25 20:43
RickStrahl commented #1000
• Jan 25 03:05
joemclain commented #1000
• Jan 25 01:42
RickStrahl commented #1001
• Jan 25 01:42
RickStrahl commented #1001
• Jan 25 01:41
RickStrahl commented #1001
• Jan 25 01:39
RickStrahl commented #1001
• Jan 24 23:11
• Jan 24 23:10
• Jan 24 07:51
jbridgy commented #998
• Jan 23 21:04
RickStrahl closed #991
• Jan 23 21:04
RickStrahl commented #991
• Jan 23 20:59
RickStrahl commented #999
• Jan 22 20:59
RickStrahl commented #1000
Gary Ewan Park
@gep13
@RickStrahl that's great, thank you!
Gary Ewan Park
@gep13
how would you feel about some companion packages on chocolatey.org, to do the download, and placement of these files into the correct location?
that way, a user could do choco install markdownmonster-en-gb
perhaps a better name would be required :-)
Rick Strahl
@RickStrahl
Sounds like a good idea. Not sure how to create a package that installs into a specific location though. It has to go into the right folder.
Maybe a package that combines a bunch of them together. Western, eastern, middle east etc. Main reason I don't ship more is that I want to keep distribution size down and the dictionaries are large.
Gary Ewan Park
@gep13
@RickStrahl yip. chocolateInstall.ps1 is just a powershell script, so anything you can do in PowerShell, you can do there. The only issue might be permissions. I was planning on doing a test to see if it could be done.
totally understand, and makes sense. Adding additional packages, that take a dependency on the main package, allow people to make an informed decision about what they want to install
Rick Strahl
@RickStrahl
Well it would have to be an admin script just like an installer as it goes into Program Files (x86) unless it's the portable version.
Another way might be to have MM look in another secondary location for dictionaries in the %appdata% folder.
Gary Ewan Park
@gep13
like I say, I will have a play, and see what I can come up with, and then we can decide how to approach it
Rick Strahl
@RickStrahl
Maybe even simpler: Put the dictionaries online somewhere, and have MM actually download them for you. That way I can do the work once and be done with it.
Gary Ewan Park
@gep13
that would work too :+1:
Rick Strahl
@RickStrahl
ie. a simple form to show installed dictionaries, and let you download others.
Gary Ewan Park
@gep13
Rick Strahl
@RickStrahl
Yes and no. The files are zipped and the may not follow the same naming conventions.
Gary Ewan Park
@gep13
ah :-(
Rick Strahl
@RickStrahl
Some have multiple dictionaries. I think we'd want to have just the dictionaries somewhere to pull down directly rather than having to sift through zip files.
Gary Ewan Park
@gep13
yip, that makes sense
Rick Strahl
@RickStrahl
I can just host it on the MarkdownMonsterReleases site that holds static content.
Gary Ewan Park
@gep13
perfect! :+1: thanks for doing that
Alex Wiese
@alexwiese
@RickStrahl is "Save As" keyboard shortcut (Ctrl+Shift+S) working for you?
Looks like it was never implemented.
Rick Strahl
@RickStrahl
Ooops :-)
Easy to fix though...
Alex Wiese
@alexwiese
Yeah I've sent through a PR
Rick Strahl
@RickStrahl
I think it was working but I took out some manual key mappings and I think that broke it at the time.
Alex Wiese
@alexwiese
OK. I found it when trying to test the changes for the H1 header/filename thing :)
Rick Strahl
@RickStrahl
I really need to go through and map everything to commands for consistency.
BTW, thanks for the PRs. Nice little additions.
Alex Wiese
@alexwiese
no problem thanks for building a great markdown editor
Rick Strahl
@RickStrahl
I know you already paid for your copy, but you would have definitely qualified for a free license :-)
Not done yet :-) Lots of things still to do.
Alex Wiese
@alexwiese
Always
Rick Strahl
@RickStrahl
Anyway just want to say I appreciate the contributions. Getting those little things done helps out a lot.
And... hopefully once a few PR's are in the bag, a few others may get involved as well.
Alex Wiese
@alexwiese
yes, exactly
Rick Strahl
@RickStrahl
Gary you got a couple of minutes for questions? :-)
Gary Ewan Park
@gep13
@rickstahl sorry, went to bed not long after last comment on issue. Will be around today if you still want to chat.
Rick Strahl
@RickStrahl
Ok that'd be cool. I think I have the portable setup all figured out. Almost ready to push it up.
Gary Ewan Park
@gep13
Is the work checked into the repo already? Happy to review prior to you pushing it out if you want?
Rick Strahl
@RickStrahl
Couple of questions
verify.txt what needs to go in there?
I don't think there's anything to see. The .ps1 is empty with all the distribution files in the .\tools folder (copied by the build process)
I have this in verify.txt:
MarkdownMonster.exe
Sha256: 3A39D79914EFD3B21BCD24F6794464F4904E4F17F23F67F414283E844945CCA1
Do I even need that if I push up the files embedded in there?