#Reddit

I'd like to share a simple CLI tool I've been developing called Cute. It's a task runner that executes commands defined in Markdown files. The key idea is straightforward: instead of learning another configuration format (YAML, JSON, Makefile syntax), you define tasks as regular Markdown code blocks. Your documentation and your task definitions live in the same place. Key features: - Pure shell script with zero external dependencies - Discovers tasks automatically from all Markdown files in your project - Supports sh, bash, zsh, and shell - Built-in fuzzy search with fzf - Tab completion for bash and zsh - No configuration required - Teams can opt-in without forcing adoption Basic usage:

A lightweight Obsidian plugin that creates citation notes from a BibTeX / BibLaTeX file. While this plugin might seem like a "re-invention of the wheel" for the Citations plugin, it is no longer actively maintained. I've developed this new plugin to be lighter, simpler, and faster. It leverages Eta as its templating engine and uses a custom-built parser for BibTeX entries. submitted by /u/ras0q to r/ObsidianMD

I'm thinking about an approach to improve structured error handling in Go so that it works seamlessly with slog. The main idea is to have a custom slog.Handler that can automatically inspect a wrapped error, extract any structured attributes (key-value pairs) attached to it, and "lift" them up to the main slog.Record. Here is a potential implementation for the custom slog.Handler: ```go // Handle implements slog.Handler. func (h *Handler) Handle(ctx context.Context, record slog.Record) error { record.Attrs(func(a slog.Attr) bool { if a.Key != "error" { return true }

[Resolved] Obsidian team is now developing ESlint plugin! https://github.com/obsidianmd/eslint-plugin I have developed several plugins for Obsidian, and every time I submit them to obsidian-releases, I am warned by the Review BOT and reviewer joethei that the code violates the style guide. I am careful every time, but there is always some flaw in the code, and this flow is burdensome for both myself and the reviewers. Is there any way to locally find common errors that the Review BOT warns about? If you know of a GitHub Actions action or linter that could serve this purpose, please let me know. submitted by /u/ras0q to r/ObsidianMD [link] [comments]

Hey there! I’m working on Ogent, a plugin that brings LLM agents right into your Obsidian workflow. Think ChatGPT, but it can actually read, create, and edit your notes, run shell commands, and trigger Obsidian commands—all from a sidebar chat. ⚠️ This project is still in early development! Expect bugs, missing features, and rapid changes. Feedback and PRs are super welcome! Repo: ras0q/obsidian-ogent

A month after the post in which I informed you that I was developing a plugin to clip academic papers to Obsidian Vault, the plugin has finally been released and now has more features! Save PDFs and their reference notes using DOI Import browser PDFs into vault with a bookmarklet

You can install fish 4.0.0 with some package managers! shell aqua g -i fish-shell/fish-shell shell mise use -g aqua:fish-shell/fish-shell submitted by /u/ras0q to r/fishshell

submitted by /u/ras0q to r/ObsidianMD [link] [comments]

submitted by /u/ras0q to r/Deno [link] [comments]

submitted by /u/ras0q to r/ObsidianMD [link] [comments]

submitted by /u/ras0q to r/ObsidianMD [link] [comments]

submitted by /u/ras0q to r/ObsidianMD [link] [comments]