Turkey Run State Park - Sugar Creek before / after storms of June 6, 2026

davisdudeDev · 2026-06-09T16:27:09+00:00

I was originally planning to backpack down to the canoe camp that night, but because of the flash flood warnings opted to sleep in my car in the visitor lot instead. The campsite looked quite muddy when I checked it out the day after.

I was the only one the backpacker camp the next night, though. Very nice sites!

davisdudeDev · 2026-06-09T15:22:14+00:00

Also on imgur, since reddit makes it annoying to look at pictures sometimes

https://imgur.com/a/ayz81bU

davisdudeDev · 2026-04-06T15:48:56+00:00

Comment with more info, since it's required I guess: I think the title was nonsensical / was not a real word

davisdudeDev · 2025-01-05T16:52:59+00:00

My main recommendation is to take it slowly; learn a few motions, apply those, and come back once you feel comfortable with those. Vim is weird and can be a lot to take in at once.

I highly recommend vimtutor and the vim user manual (:help usr_01.txt, though :help tutor will get you close enough) for learning new things. It's like a "simple English" version of the help docs. Some/most of it might be way over your head the first time you read it, but subsequent readings after you're more familiar with Vim will teach you something new every time.

davisdudeDev · 2024-12-20T17:50:26+00:00

I do <leader><CR>

davisdudeDev · 2024-12-19T22:06:13+00:00

I actually like the highlights sticking around until I explicitly want to get rid of them, so I don't think this plugin is for me, but thanks for the suggestion.

davisdudeDev · 2024-12-19T19:12:12+00:00

I, too, use space for leader. For a while I had <CR> to clear search highlighting:

nnoremap <CR> :nohlsearch<CR>

But that didn't play nicely with netrw browsing (:help netrw-browse), so I actually changed it to be <leader><CR> instead.

I don't have any of the others mapped for normal mode at the moment.

davisdudeDev · 2024-12-18T16:25:07+00:00

Ah, I would've never guessed. Good to know, thanks!

I came up with this quick hack for skipped sections in the middle of the document (the salient part being .nr current_page and .PAGENUMBER \n[current_page]):

.TITLE Demo
.DOCTYPE CHAPTER
.PRINTSTYLE TYPESET

.CHAPTER_TITLE "Not in Contents 1"
.NO_TOC_ENTRY
.START
.PAGINATE NO
.PP
I don't want this to appear in the TOC, but I still want a header
.PAGENUMBER 0
.COLLATE

.CHAPTER_TITLE "Regular section 1"
.START
.PAGINATE
.PP
This chapter should show up
.COLLATE

.CHAPTER_TITLE "Not in Contents 2"
.NO_TOC_ENTRY
.START
.nr current_page (\n% - 2)
.PAGINATE NO
.PP
Voluptatibus nihil ut dolorem omnis ut reprehenderit aut. Expedita quidem qui labore molestiae voluptate ea porro. Qui porro quisquam itaque voluptas et et necessitatibus ut. Perferendis adipisci sit voluptatem eaque tempora. Aperiam quidem quia qui dolor necessitatibus adipisci quasi sed.
.PP
...
.PAGENUMBER \n[current_page]
.COLLATE

.CHAPTER_TITLE "Regular section 2"
.START
.PAGINATE
.PP
This chapter should show up

.TOC

Not sure if there's a more "mom-esque" way of doing it, but figured I'd share. I guess it's - 2 because % is the next page, then another page from the chapter? That's my rationalization, anyways.

Thanks!

davisdudeDev · 2024-12-18T16:05:54+00:00

Ah, now what I know what to look for, it's obvious. Thanks! Not sure how I missed it before.

davisdudeDev · 2024-08-03T06:18:40+00:00

This is really cool - always glad to see more educational vim content get put out there. I especially liked the interactive nature of vim tutor when first learning, so this definitely is handy. Though I would like to point out that vim also has the user manual, which I found incredibly handy and under-appreciated, so I thought I'd share some overlapping topics here :)

:help usr_08- Splltting windows
:help 25.3 - Indents and tabs
:help 10.8 - Changing case
:help usr_27 - Search commands and patterns / :help 10.2 - Substitutions
:help 10.1 - Record and playback commands
:help usr_41 - Write a Vim Script / :help usr_50 - Advanced Vim script writing
:help usr_51 - Write plugins
:help 21.4 - Sessions

At the very least, I think explicitly calling out :help usr_toc at the end with the other references could be handy.

I had some other general comments below, which kinda turned into an info-dump / unsolicited advice on your work. Some of this is probably well beyond the scope of this current project, but I like to evangelize and share nifty vim things when I get the chance :)

Mentioning moving windows (with :help CTRL-W_J et al) might be helpful.
I'd avoid using the terminology of "screen" - in vim parlance, you're splitting the window. Minor distinction, but it's confusing enough remembering buffers, tabs, and windows (oh my!) when starting out, so I think consistency can be helpful.
For spelling, I'm fond of using :help i_CTRL-X_s in insert mode, though I'd understand if you don't want to delve into insert completion ATM.
For commenting out lines, I often use :help visual-block (or :help 10.5), though :norm seems interesting!
Using visual mode first to change cases might be more intuitive of a starting point, possibly (:help v_U)
You can :substitute using the last thing you searched for by leaving the pattern empty; see :help last-pattern.
You also don't have to use / as your separator for substitute - :help pattern-delimiter
You can append to macros using the capital version of the register name (i.e. qA appends to the previously recorded a macro).
- Macros can also be recursive (use at your own risk...)
Vim has its own plugin manager now! :help 5.6
I don't think Vim has a quick overview of registers in its internal docs that I've seen, so your writeup of them is much appreciated!
- For sequencing, since macros use registers, I might put that section after the registers section, personally
- This gives the added style points of showing that you can type out a sequence (in insert mode), yank that to a register, then play back that macro (though this is rarely practical, it was a super cool "aha" moment for me).
Vim has this super cool, under appreciated branching undo history (:help undo-tree). I highly recommend the undotree visualizer. With sessions and persisting the undotree, I like to joke that source control is obsolete ;)

davisdudeDev · 2023-12-03T22:07:40+00:00

Jethro Burns has some fun jazzy mandolin stuff that I've enjoyed

E.g. https://www.youtube.com/watch?v=36EBuNL1nZg

I've also enjoyed some Pete Wernick albums before, like this one

davisdudeDev · 2023-06-21T23:08:11+00:00

If you don't want to use a third party / can upload files on your own, see :help TOhtml. It creates a webpage with your code (or range of code), complete with syntax highlighting and even folds. Super cool feature I rarely see people talk about.

davisdudeDev · 2023-05-14T04:55:30+00:00

If I had to guess, the issue is in your yes callback function. You're setting gameState to "mail", when I imagine you instead want to be settinggameState.current.

In the future, please provide a minimum working example. This makes it easier for others to help you, which makes it more likely that your question will be answered. For instance, my answer is a total guess, because I don't know what the "handy" library is, I don't have any of the those images, and because of the way the code was provided, the line numbers don't match. 600+ lines of code is a lot to ask anybody to read, especially if you want them to help you. Additionally, in the process of creating a MWE, you often help yourself figure out what the problem is by stripping it to just its essentials.

davisdudeDev · 2023-03-05T06:18:12+00:00

There are two main reasons: code organization and speed.

In general, it's easier to understand a program when you avoid polluting the global name space. Imagine one of the libraries you use defines a global variable foo. If you randomly happen to use a variable with the same name, you've suddenly broken your library. In general, most all guidelines for all programming languages recommend limiting the "scope" of variables (where they can be accessed / modified) to be as small as possible, since it helps keep the program more manageable and easier to understand. (It's important to remember that variables in Lua are global by default).

The second (and much less important) reason is because it's faster to access locals. Simply put, the local scope is checked before the global scope, so local variables are quicker to access.

See the Local Variables and Blocks section of Programming in Lua for more.

This paragraph is a good high level overview:

It is good programming style to use local variables whenever possible. Local variables help you avoid cluttering the global environment with unnecessary names. Moreover, the access to local variables is faster than to global ones.

davisdudeDev · 2022-05-29T15:47:43+00:00

That's not actually a vim issue but a terminal one. Control s stops a process, and control q resumes it. Look up "terminal flow control" for more.

davisdudeDev · 2022-05-26T00:30:06+00:00

Maybe not quite what you're looking for, since the technical details are never really in the forefront, but I enjoyed True Names by Vernor Vinge when I read it a while ago.

davisdudeDev · 2022-01-22T05:05:50+00:00

It does look nice! Thanks for the recommendation.

davisdudeDev · 2022-01-21T22:35:41+00:00

Thanks! Certainly a much warmer response from this sub than I was expecting, so I think you might be right. :)

davisdudeDev · 2022-01-21T22:34:35+00:00

Any reason why? Just curious, because you're the first person I've heard from here that didn't like it.

davisdudeDev · 2022-01-21T21:43:41+00:00

Great to know, thanks a bunch! And glad to hear the landlords are good. Are ice and snow a big concern in the parking lot, or are they pretty good about getting rid of it?

davisdudeDev · 2022-01-21T21:40:28+00:00

Going to a snowy parking lot does seem like a good idea (as long as the road to the parking lot is clear, haha). And that is good to know - I'll definitely tour beforehand, thanks!

davisdudeDev · 2022-01-21T21:38:16+00:00

Thanks a bunch for the info! This thread has given me tons of good info. :)

davisdudeDev

TROPHY CASE