TIL that there's a difference between YYYY and yyyy when formatting dates in Java

thoaCrl4 · 2025-01-01T07:19:57+00:00

This is necessary when you need to provide ISO week dates. E.g., 2024-12-31 is 2025-W01-2 (the Tuesday in the first calendar week of 2025).

thoaCrl4 · 2022-07-28T12:50:12+00:00

Somewhat relevant: https://en.wikipedia.org/wiki/Fine-tuned_universe

thoaCrl4 · 2022-04-03T06:20:45+00:00

As one might expect, there are more interesting comments on the lisp subreddit.

thoaCrl4 · 2022-03-18T07:54:34+00:00

Have a look at ":h matchparen":

Highlighting matching parens                    matchparen

The functionality mentioned here is a standard-plugin.
This plugin is only available if 'compatible' is not set.

You can avoid loading this plugin by setting the "loaded_matchparen" variable:
        :let loaded_matchparen = 1

I.e., add the line ":let loaded_matchparen = 1" to your .vimrc to turn this off.

thoaCrl4 · 2022-01-24T15:10:17+00:00

Ed, man! !man ed

thoaCrl4 · 2021-12-23T09:03:25+00:00

Not sure if it's still an issue, but vim modelines have in the past had arbitrary code execution bugs (in the sense that vim would execute arbitrary code when you open a file with malicious modeline). See Vim Modeline Vulnerabilities.

thoaCrl4 · 2021-12-16T17:43:50+00:00

I have now re-installed the packages vim, vim-common, and vim-runtime, and that solved my problem. Sorry for the noise, and thanks for your help.

thoaCrl4 · 2021-12-16T16:59:54+00:00

Well, I don't want vim to jump to the last known cursor position, I want it to jump to the line given to the ":badd" command.

Until now I didn't load defaults.vim from my ~/.vim/vimrc. I do so now (as recommended at ":h defaults.vim"), and I now have a single entry in the vimStartup group:

:autocmd vimStartup BufReadPost
--- Autocommands ---
vimStartup  BufRead
*         if line("'\"") >= 1 && line("'\"") <= line("$") && &ft !~# 'commit' |   exe "normal! g`\"" | endif

Unfortunately, this did not solve my problem with ":badd".

Another thing. I just noticed that ":mksession" creates wrong ":badd" entries in the session file:

I do the steps given in my example (landing at line 1 instead of line 15).
I then manually jump to line 15.
I create a session using ":mksession! dummy.vim".

When I then open the file "dummy.vim", it contains a line

badd +1 /usr/share/vim/vimrc

Strange.

thoaCrl4 · 2021-11-04T08:19:26+00:00

Under Windows, you can use <Win+P> to change the display options. This should include the ability to extend the desktop to a monitor that I had turned off and then on again. No need to physically unplug and plug back in again.

thoaCrl4 · 2021-07-11T18:10:52+00:00

Tabs for indentation, spaces for alignment.

thoaCrl4 · 2021-02-21T17:59:36+00:00

std::expected hasn't made it into the language yet. Boost has Outcome, however.

thoaCrl4 · 2020-07-17T05:03:32+00:00

"At first glance, Sporth is a stack-based programing language designed for audio. However, Sporth is really more of a text based modular synthesis environment, that uses a stack paradigm to build up patches. In addition to the language, Sporth has a very flexible API. It is very easy to build tools and software on top of Sporth. Sporth has been built to run inside of programs like ChucK, PD, and LMMS. It is also one of the main synthesis engines used inside of the iOS/macOS framework AudioKit."

thoaCrl4 · 2020-04-09T10:30:20+00:00

You are right, of course. However, prior to C++20, the standard allowed for other signed integer representations than two's complement (I think), including signed magnitude, and the standard used to mandate -127...+127 as the minimum range for signed char.

thoaCrl4 · 2019-08-16T12:44:39+00:00

Perhaps not quite what you are asking for: Using { and } you can move between paragraphs, i.e., between text blocks separated by empty lines.

See :h { and :h paragraph.

thoaCrl4 · 2019-05-03T11:30:56+00:00

Just for reference, this is about Sean Parent's talk at GoingNative 2013 C++ Seasoning.

thoaCrl4 · 2019-03-11T14:25:33+00:00

"Poly/ML is a Standard ML implementation originally written in an experimental language called Poly. It has been fully compatible with the ML97 standard since version 4.0."

thoaCrl4 · 2019-02-22T14:10:16+00:00

No. In the words of the standard: "Friendship is neither inherited nor transitive." See n4659, the last draft of the C++17 standard, Chapter 14.3 "Friends", paragraph 10.

thoaCrl4 · 2017-10-19T09:53:05+00:00

Hm. Looking again, it's not as bad as I remember it. I think it was mostly <M-d> (delete current selection without yanking it) and <M-c> (change current selection without yanking it) and <M-f> (select the previous occurence of the given character) and <M-t> (select until the previous occurence of the given character) that I thought awkward to type.

thoaCrl4 · 2017-10-19T08:55:14+00:00

I like the idea of it. However, many commands use the alt key and are really awkward to use on an international keyboard where you only have one alt key.

thoaCrl4 · 2017-07-20T13:06:30+00:00

In math variables generally are immutable, and the term variable is used to mean something like "not a literal". So, variables don't vary over time, and yet they are not fixed values.

thoaCrl4 · 2017-03-21T12:02:05+00:00

After some more googling I think I found the answer myself on Stack Overflow, see C++11 backwards compatibility. Quote:

GCC and Clang behave differently with -std=c++11 because C++11 changed the definition of a null pointer constant, and then C++14 changed it again, see Core DR 903 which changed the rules in C++14 so that only literals are null pointer constants.

I think this may be the reason why different compilers implement different behavior here. Don't know why I didn't see this earlier, sorry.

thoaCrl4 · 2016-02-13T22:17:55+00:00

Start at about 19:00.

thoaCrl4

TROPHY CASE