Vim setup

[jklebes]

Short basic version

I also had these ideas, which I consider essential:

Since fortran is case-insensitive, set vim's search to ic (ignore case) by adding to ~/.vimrc

set ic

To set vim to remember what line we were on when opening files, add the following to ~/.vimrc:

" Remember cursor position
if has("autocmd")
  au BufReadPost * if line("'\"") > 1 && line("'\"") <= line("$") | execute "normal! g`\"" | endif
endif

Thoughts?

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/carpentries-incubator/intro-to-modern-fortran/compare/md-outputs..md-outputs-PR-54

The following changes were observed in the rendered markdown documents:

 links.md   |  3 +++
 md5sum.txt |  4 ++--
 setup.md   | 28 ++++++++++++++++++++++++++--
 3 files changed, 31 insertions(+), 4 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2025-11-28 15:38:33 +0000

[vahtras]

I would not have ignore-case as a general rule. For Fortran files it makes sense, with something like

au BufNewFile,BufRead *.F90 set ic