Recent Changes

2019-09-08

• 20:41 UTC (new) (history) 2019-09-08 PostgreSQL and computing the number of days between two dates . . . . Marcin Borkowski – A few days ago I had a very interesting bug. (Frankly, it’s nothing to be proud of, but it’s interesting and also kind of funny, so I thought I’d share it.) I had a long PostgreSQL query which – as one of many conditions – checked if some date was more than two weeks in the future.
• 20:37 UTC (diff) (history) Comments on 2019-08-05 datefudge and agenda testing . . . . Marcin Borkowski – Exactly - but I think {{{datefudge}}} may be more robust.
• 20:36 UTC (diff) (history) Comments on 2019-06-24 org-agenda-todo-ignore-timestamp vs org-agenda-todo-ignore-with-date . . . . Marcin Borkowski – I know, but I was too lazy to explore it;-).
• 20:35 UTC (diff) (history) Comments on 2019-01-20 Filling and version control . . . . Marcin Borkowski – Interesting, thanks!
• 20:35 UTC (diff) (history) Comments on 2019-08-31 A simple tip with overlays and diffs . . . . Marcin Borkowski – Thanks, but not. It solves a different problem - it goes to the next hunk, and I wanted to go to the next change even /within/ the current hunk.

2019-08-31

• 11:17 UTC (new) (history) 2019-08-31 A simple tip with overlays and diffs . . . . Marcin Borkowski – A few days ago I had an interesting problem. I had to resolve a particlarly nasty Git merge. It involved several files with lines’ lengths in the triple digits and a fair number of very small changes. Seeing those changes (in smerge-mode), even after refining the diffs, was tricky – there were many very small patches (sometimes two, sometimes four characters) of changed text and I was quite afraid that I would miss some of them. I searched for a command to “go to the next patch of changes”, but to no avail. Then I decided to write my own.

2019-08-26

• 20:42 UTC (new) (history) 2019-08-26 PostgreSQL – COALESCE and NULLIF . . . . Marcin Borkowski – After the last week’s long post I decided that I needed some rest, so today I only have a short tip. It is a common need to say that we want the value of some variable x unless it is some kind of null value (depending on the language we use), in which case we want the value of some other variable y. The Lisp idiom for that is of course (or x y). In JavaScript, we usually say x || y, although this is risky if 0 is a valid value of x. (Hopefully, we will be able to say x ?? y in JS soon.) In my case, however, I needed this in SQL (more specifically, in PostgreSQL, but that doesn’t matter now).

2019-08-19

• 20:56 UTC (new) (history) 2019-08-19 Transplanting a directory to another Git repository . . . . Marcin Borkowski – Recently, I had a very specific need. I wanted to move a directory to another Git repo, but I really needed to preserve its history.

More...