Newest at the top
2025-09-18 10:59:21 +0200 | <tjakway> | I did think it was kind of amusing that I never actually used it as an SCM, just for its issue tracker |
2025-09-18 10:58:42 +0200 | <tjakway> | It had a very easy wiki syntax and D. Richard Hipp writes very good software |
2025-09-18 10:57:47 +0200 | <tjakway> | so I could make tickets for myself on things to do and link notes to them |
2025-09-18 10:57:19 +0200 | <tjakway> | I actually used the fossil SCM as a personal ticketing system and it worked very well |
2025-09-18 10:56:17 +0200 | <tjakway> | maybe I could come up with a good submodule solution |
2025-09-18 10:56:08 +0200 | <tjakway> | Yes, and I'm very forgetful, so I'll admit I don't like the idea of my notes being scattered about so many different git repos |
2025-09-18 10:55:50 +0200 | <jreicher> | Some kind of list you can browse, and then jump to the detail. |
2025-09-18 10:55:31 +0200 | <jreicher> | So that one is more about indexing I think. |
2025-09-18 10:55:19 +0200 | <jreicher> | I find knowledge notes more difficult, because sometimes you've forgotten what you might want to look up. |
2025-09-18 10:54:42 +0200 | <tjakway> | or markdown or what have you |
2025-09-18 10:54:36 +0200 | <tjakway> | jreicher: I was thinking about that too, and LaTeX makes that much easier |
2025-09-18 10:54:13 +0200 | <jreicher> | Personally I would keep notes about a project IN the project. |
2025-09-18 10:54:11 +0200 | <tjakway> | that goes in the "C++ Notes" file but I'm going to link it to my C++ project-specific notes where relevant |
2025-09-18 10:53:37 +0200 | <tjakway> | for example, I was taking notes today on designing C++ iterators (which is WAY more complicated than I thought) |
2025-09-18 10:53:00 +0200 | <tjakway> | jreicher: it depends, because I have a lot of different kinds of notes: some are directly about projects, others are more knowledge but relevant to projects |
2025-09-18 10:51:32 +0200 | <jreicher> | tjakway: what typically leads you to retrieve your notes? (Not write them.) I find the organisational principle is given by the retrieval cases, not by the recording cases. |
2025-09-18 10:50:44 +0200 | PKDrinker | (~PKDrinker@user/PKDrinker) (Remote host closed the connection) |
2025-09-18 10:50:31 +0200 | gmg | (~user@user/gehmehgeh) gehmehgeh |
2025-09-18 10:47:03 +0200 | chromoblob | (~chromoblo@user/chromob1ot1c) chromoblob\0 |
2025-09-18 10:46:36 +0200 | chromoblob | (~chromoblo@user/chromob1ot1c) (Read error: Connection reset by peer) |
2025-09-18 10:46:34 +0200 | noctux | (~noctux@user/noctux) (Read error: Connection reset by peer) |
2025-09-18 10:45:42 +0200 | Square2 | (~Square@user/square) Square |
2025-09-18 10:43:54 +0200 | Fischmiep | (~Fischmiep@user/Fischmiep) Fischmiep |
2025-09-18 10:41:49 +0200 | <dontdieych> | 'Dolphin on ~/Downloads' is basically big wiki index to me |
2025-09-18 10:41:12 +0200 | Fischmiep | (~Fischmiep@user/Fischmiep) (Quit: ZNC - https://znc.in) |
2025-09-18 10:38:09 +0200 | <dontdieych> | tjakway: I'm mostly do not organize things. just save it in ~/Downloads (or wherever) or somewhere. `ls -rt1`, `fd ... | fzf` or `ctrl-f` in gui file manager is good enough for me. :D |
2025-09-18 10:34:43 +0200 | PKDrinker | (~PKDrinker@user/PKDrinker) PKDrinker |
2025-09-18 10:32:57 +0200 | <defragger> | i am using vimwiki for years now |
2025-09-18 10:30:21 +0200 | inline | (~inline@2a02:908:1246:c0c0:f592:a505:c001:e7a3) Inline |
2025-09-18 10:29:26 +0200 | <tjakway> | and every time I open it I despair of how much time I've spent writing bash |
2025-09-18 10:28:34 +0200 | <tjakway> | too many snippets to trust formatting to word |
2025-09-18 10:28:22 +0200 | PKDrinker | (~PKDrinker@user/PKDrinker) (Ping timeout: 244 seconds) |
2025-09-18 10:28:16 +0200 | <tjakway> | I actually do that right now for bash |
2025-09-18 10:28:10 +0200 | ljdarj | (~Thunderbi@user/ljdarj) ljdarj |
2025-09-18 10:28:08 +0200 | <tjakway> | dontdieych: one BIG markdown file ;) I have a lot of notes... |
2025-09-18 10:27:20 +0200 | <dontdieych> | tjakway: just one big markdown file ( folding and toc view good for fast navigation) |
2025-09-18 10:23:50 +0200 | APic | (apic@apic.name) APic |
2025-09-18 10:23:50 +0200 | PKDrinker | (~PKDrinker@user/PKDrinker) PKDrinker |
2025-09-18 10:23:21 +0200 | <probie> | I use org-roam, but if you don't want to use emacs, I hear good things about Obsidian |
2025-09-18 10:22:41 +0200 | gentauro | (~gentauro@user/gentauro) gentauro |
2025-09-18 10:22:07 +0200 | APic | (apic@apic.name) (Ping timeout: 260 seconds) |
2025-09-18 10:20:59 +0200 | gentauro | (~gentauro@user/gentauro) (Ping timeout: 260 seconds) |
2025-09-18 10:20:27 +0200 | Sgeo_ | (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |
2025-09-18 10:18:59 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 260 seconds) |
2025-09-18 10:16:42 +0200 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
2025-09-18 10:14:59 +0200 | Googulator | (~Googulato@2a01-036d-0106-217b-9021-558a-ccea-f5e8.pool6.digikabel.hu) |
2025-09-18 10:14:44 +0200 | Googulator | (~Googulato@2a01-036d-0106-217b-9021-558a-ccea-f5e8.pool6.digikabel.hu) (Quit: Client closed) |
2025-09-18 10:13:43 +0200 | <tomsmeding> | I use a notes.txt file in the relevant git repo for the project if applicable, otherwise markdown notes in a syncthing-synchronised folder (that I view with Obsidian, but I don't use any of the fancy functionality) |
2025-09-18 10:10:58 +0200 | mreh | (~matthew@host86-146-25-35.range86-146.btcentralplus.com) |
2025-09-18 10:10:47 +0200 | <tjakway> | Right now I file everything in Google Drive but I'm very unhappy with its lack of Linux support and Latex could also lead to filing everything in git instead... has anyone else done this? |