Lmst

Has anyone had good experiences with (universal) ctags for PHP? Looking for a solid, non-plugin, vim-native LS alternative for vim (9.1).

I tried `ctags -R --language-force=PHP --php-kinds=+c-f --fields=+n` as well as setting tags `set tags=./tags;,tags` but vim can't jump to function declarations by tag.

#vim #vim9 #ctags #UniversalCtags #php

Стилистический Анализатор: Синхронизация Объявлений и Определений static Функций

Представлена утилита проверяльщик, что последовательность определения static функций совпадает с последовательностью объявляения static функций.

https://habr.com/ru/articles/846020/

#static #ctags #sed #awk #cmp #code_style

Стилистический Анализатор: Синхронизация порядка объявлений и определений функций

У нас в организации есть обязательное правило оформления исходников, которое звучит так: Порядок объявления С-функций должен совпадать с порядком определения С-функций. В этом тексте представлен алгоритм работы консольной программы, которая автоматически выявляет нарушения этого странного правила.

https://habr.com/ru/articles/844436/

#ctags #awk #gawk #sed #cygwin #cmp #gcc #статический_анализ #стилистический_анализ #static_analysis

This is how I integrate rusty tags in my .zprofile:

# rusty-tags
[ `command -v rustc` ] && RUST_SRC_PATH=$(rustc --print sysroot)/lib/rustlib/src/rust/library/
[ -d $RUST_SRC_PATH ] && export RUST_SRC_PATH

I still prefer #ctags over LSP.

#rust #rustlang

Removed #LSP shenanigans from my #nvim config. I don't really care about it and I hate to need external demons to make text editor do its job. It is even worse than plugins, which I neither love. And I never use auto-complete because it does stuff faster than my head can keep up.

Overall for me #ctags is still best possible experience when indexing source code. It crawls deep, does not do anything automatically and does not require external 3rd party prgrams.

And yeah it is stupid as hell, and thus can index whole #Linux tree without trying to understand it. With LSP indexing is build config dependent, which makes it crippled.

With #Rust I use rusty-tags: https://github.com/dan-t/rusty-tags

@here_for_code @evilmartians I like #standardrb because it uses #RuboCop but only implements basic and non-controversial rules that help with linting.

I occasionally use #RubyMine for the (putatively) automated refactorings and to play around with #AI integrations, but I'm a #CLI guy and don't find IDE's very intuitive. I use heavily customized #vim, #ack or #thesilversearcher, and #ctags for day to day stuff. It just seems faster to me, but that could just be muscle memory and habit. 😄

I always return to #ctags once tried on LSP. E.g. it does not have dependency hell bundled. It always works as expected. Even with LSP I always disable auto-complete, which takes away a lot of its value, assuming that you care about this feature in the first place.

#ctags and/or #cscope are tbh better options for browsing #kernel than #clangd because two former ignore kernel config/build when scanning for new tags. perhaps get_compile_commands.py could be improved a bit. #linux

Using an #LSP server in #neovim for working with #Moodle has accelerated my workflow, but from time to time jumping to certain function declarations fails while still pushing one CPU core to 100 percent.

Maybe #phpactor is unfit for Moodle’s codebase? It also gives many false errors.
I might try #phan or #psalm instead, or even just use #ctags again.

#php #nvim #webdev

I’ve been using #ctags with #ledger for a couple months now. It’s been a complete game changer to update my journal with fast completions and code navigation. It works out of the box with my editor of choice #neovim/#vim and also with other editors, sometimes with a plugin (#emacs, #vscode…).

I’m now sharing the ctags configuration, as this could benefit others: https://cj.rs/ledger-ctags/

Please let me know if you have issues or if some things are unclear!

🏦 #plaintextaccounting #ledgercli

🧵1/4

#til about #ctags in #vim ...
How did I live so long without knowing this existed?
Now I am wondering if there are other methods for this type of "drilling down" in #nvim

#Makeheaders is a #C header file generator.

Makeheaders scans C or C++ source files for public definitions and creates header files containing prototypes for found definitions. Makeheaders enables integration of both the interface and implementation into a single file which is automatically expanded into the two files. Makeheaders is very fast, works with make, and can work as #Ctags.

Website 🔗️: https://www.hwaci.com/sw/mkhdr/

#free #opensource #foss #fossmendations #programming #Cpp

#UniversalCtags is a #Ctags implementation for many languages.

Universal Ctags examines a source code file for any symbols (variables, types, functions) and outputs a tagged list of those symbols for use in an editor like #Vim or #Emacs. Universal Ctags can parse many languages, including #C, #Python, #Rust, and #COBOL. Universal Ctags supports various output formats.

Website 🔗️: https://ctags.io/

apt 📦️: universal-ctags

#free #opensource #foss #fossmendations #programming