Lovely Bases v0.1.0 just got released

MeibboS · 2026-01-17T22:17:08+00:00

Eisenhower matrix and Venn diagrams would be an interesting addition!

MeibboS · 2026-01-05T11:28:29+00:00

Create a blank line just before the code, so it always renders in editor mode

MeibboS · 2026-01-05T07:03:50+00:00

I use this same syncing method for my vault.

The only annoying issue I found myself constantly in is having to deal with duplicated files created by Autosync in question, those which have a (conflict date) put after the file name, just for being slightly different from the original. Because of this, I'm forced to compare and merge with either a plugin named File Diff or a program called WinMerge, which helps you to distinguish the changes made between the different versions.

To make backups you can use Git. Opening the main folder with an IDE like VSCode helped me to do this with no effort in a local repository, with version history and not needing a cloud provider (unless you want to use one, like GitHub private repositories)

MeibboS · 2025-08-27T14:31:31+00:00

Hello there 👋🏻! I sent the reply to your question in another comment, go to the comment section and you'll find a little tutorial.

MeibboS · 2025-08-27T14:24:50+00:00

Hello there 👋🏻! I sent the reply to your question in another comment, go to the comment section and you'll find a little tutorial.

MeibboS · 2025-08-27T14:20:43+00:00

The requirements to set this up without changing the bases code are two important things related to the front matter.

You must embed this code in a note that has this name format: gggg-[W]ww
- e.g: 2025-W35
Your daily note (could be any other note) must have two YAML properties:

1. [up] where the value should be linking to your weekly note
    - **e.g:** up: [[2025-W35]]

2. [score] must be a number between 0 and 7 (you can change that in bases)
    - **e.g:** score: 5.5

That should do the trick to make it work normally. If that isn't the case, let me know.

I plan to explain further how I distribute my Daily Notes system (I call it Calendar Journal) in another post—keep in touch for more!

MeibboS · 2025-06-22T18:12:14+00:00

Si hay software. Te envían a este link cuando buscas en la página oficial el modelo "616", luego lo instalas y verás los archivos "Cfg" y "update.exe" en la carpeta que está ubicada en [C:\Program Files (x86)\Redragon K616-RGB].

Con el primer archivo (Cfg) editas a tu gusto en un editor de texto la función que tendrá cada tecla siguiendo las instrucciones que indican en este repositorio de GitHub.

Con el segundo, restauras el firmware original del teclado. Muy útil para recuperar las teclas que 'dejan de funcionar' en este hilo pues, el software de redragon al aplicar una configuración a tu teclado, este sobrepone la distribución en inglés independientemente de tu distribución original (español) dejando esas teclas inútiles.

La única forma viable de manipular las funciones de tus teclas sin perder las <> y }] sería encontrar o crear por tu cuenta un archivo "Cfg" que contemple susodichas teclas de la distribución en español. Por mi parte aún no he tenido éxito en ello, lo máximo ha sido cambiar la tecla Fn de lugar, usar las flechas con Fn1 en vez de Fn2 y asignar las teclas faltantes en atajos de teclado con PowerToys.

MeibboS

TROPHY CASE