serhii.net

Linking to blocks and headers in #obsidian

Is helpfully describeed in the autocomplete for [[:

• [[^to internal blocks (you have to type the title by yourself, like this)
• [[# for headers (Manually creating block references).
  • Can work even when linking from other pages!

EDIT 2021-12-07: You can do this from external pages too! Just autocompletion is not intuitive. See 211207-2015 Obsidian embedding parts of other document. ¹

Manually creating block references

When linking internally it autogenerates reference names, it seems. ^74ce58

Can I do this? ^myreference

Yes I can! Autocompletion even suggests/uses my reference!

Can _I_ do this? ^myreference

[Yes I can!](#^myreference)  Autocompletion even suggests/uses my reference!

When looking at a commit, clicking on “View the entire source for this file” symbol opens that file, and then one can navigate to folders etc as usual, they’ll all be from the current branch.

Hugo generates anchors from headers automatically ¹. Tested it - yes, except they’re lowercased and spaces get converted to - (which makes sense).

As a refresher, in HTML it’s

<h2 id="anchor">..</h2>
<a name="anchor"></a>

<a href="#anchor">anchor link </a>

One additional way to check the type hints in #python is mypy, installable as python package.

mypy -p package_name checks the typing in the package, and found some potential errors in corner cases I didn’t know about in one of the projects I’m working on!

Finds wrong typing, missing/wrong return values, that kind of stuff.

It doesn’t like what: str or Path typing output, I guess only Union[str, Path] - is there a reason for it?

In any case I like it more than Pycharm’s way of outputting things and will be using it along with black and flake8 in the future (along with typing itself).

#py/mypy

Tried to download a Teamcity artifact through wget, and apparently you can if you provide a user/pass through wget!

I assume it’s HTTP auth or something

wget --user username --password my-password https://teamcity.location/repository/download/....

Had issues, asked for help, and then learned a lot of stuff.

git rebase branchname != git rebase origin/branchname!

The first one is about the current local state of the branch, the second one about the one on remote.

BUT the one on remote as known by local != one on remote-remote! You need to update first!

git fetch --all or whatever.

I’d previouly update / pull before through PyCharm before doing that, and this abstracted all of this away from me.

To access the #obsidian console, <C-S-i> worked. It was the standard “Dev tools”.¹

Since I seem to keep forgetting: simple-scan is the program I use to talk to scanners. You can select various options (scan document, photo etc).

Keeps #scanning in the exact same PDF document until you break it.

In #pycharm, “Pin tab” exists! But then it’s not “Tab 1” etc anymore and I can’t use my shortcuts

(Those too after a long talk to a colleague at work, this time #py/argparse)

Cool things about argparse:¹

• parser.add_argument('--two-words') would automatically map to args.two_words (_ vs -)!
• One can provide complex types!² For files, two options.
  • The first one allows to set file permissions etc., but it opens them and returns the handle to you, which you may not want.
  • pathlib.Path() works as expected, and even automagically parses string paths from args into the Path!
    • Additionally we can then establish that we’re working with Paths from the very beginning, getting rid of the str or Path ambiguity.

    • “Be strict and clear from the very beginning, then you don’t have to deal Path or str”

  • Sample of both from official documentation:

    parser.add_argument('a', type=argparse.FileType('w', encoding='latin-1'))
    parser.add_argument('b', type=pathlib.Path)
    

• You can get defalut values from os.environ()! Then you can also run it as

  WHATVEER_VALUE=234 python3 file.py
  

A nice structure for it all is:

1. if __name__ == '__main__': runs a function like main() getting rid of the scope issues
2. Parsing is done my a separate function, that returns the Namespace:

   def parse_args() -> argparse.Namespace:
       parser = argparse.ArgumentParser()
       parser.add_argument('--input-directory' ..)
       return parser.parse_args()
   

3. Then in main() we use it like args = parse_args(); if args.input_directory == ... This is nice also because then we don’t have to deal with an arparse object in main, just its results.

Also, in general, CLI programs have arguments like program --arg-one, not program --arg_one. I write the latter one because I still feel I’m in a python world, but Python would parse such dashed arguments into classic ones (see above). TODO look for some best practices for CLI programs, including Python ones, POSIX etc etc etc.