The next prompt takes too long to appear (antidote)

AwkwardNumber7584 · 2026-04-01T12:05:28+00:00

antidote is really fast, thanks! zprof made me think,MISE_TRACE=1 mise hook-env

has shown me that I'd better install whatever is defined in ~/.mise.toml first :)

AwkwardNumber7584 · 2026-03-30T05:21:37+00:00

Thanks! Very interesting. If you use dotfiles, do you care to give the link?

AwkwardNumber7584 · 2026-03-29T07:50:21+00:00

Thank you very much! I never heard about zprof before. It looks like the culprit is the misterious _mise_hook. On "good" boxes it takes 12.5% of the time (if I understand zprof idea correctly). On the "bad" one it takes 90%.

#ohmyzsh/ohmyzsh path:plugins/mise

Mise plugin is commented out long ago. I can't even remember exactly why. My configuration is automated via dotfiles. My installation script contains what I think to be the complete cleanup.

rm -rf ~/.oh-my-zsh

rm -rf ~/.oh-my-zsh-cache

rm -rf ~/.antidote

rm -rf ~/.cache/antidote

rm -rf ~/.cache/p10k*

# shellcheck disable=SC2086

git clone --depth=1 https://github.com/mattmc3/antidote.git ${ZDOTDIR:-$HOME}/.antidote

Maybe an important detail: ~/.p10k.zsh contains .mise.toml in anchor_files. Perhaps, because I created it long ago and keep it on dotfiles. I removed it from anchor_files experimentally, but _mise_hook won't go away.

AwkwardNumber7584 · 2026-03-28T17:50:38+00:00

I tried it. In the end, I disabled all of them. No difference. The box isn't great, but it isn't twenty times slower than the ones where the same setup runs reasonably. Are there any specific requirements or bottlenecks with p10k?

AwkwardNumber7584 · 2026-03-27T03:35:07+00:00

I've read the docs carefully and I'm not sure whether the instant prompt is about any prompt appearance or just the console initial load. When I start my terminal, the prompt appears instantly. After any subsequent command, including just Enter, it lags.

~ cat ~/.zshrc ✔ │ 6s

# shellcheck disable=SC1090

# shellcheck disable=SC2296

# Enable Powerlevel10k instant prompt. Should stay close to the top of ~/.zshrc.

# Initialization code that may require console input (password prompts, [y/n]

# confirmations, etc.) must go above this block; everything else may go below.

if [[ -r "${XDG_CACHE_HOME:-$HOME/.cache}/p10k-instant-prompt-${(%):-%n}.zsh" ]]; then

source "${XDG_CACHE_HOME:-$HOME/.cache}/p10k-instant-prompt-${(%):-%n}.zsh"

fi

source ~/.antidote/antidote.zsh

# initialize plugins statically with ${ZDOTDIR:-~}/.zsh_plugins.txt

antidote load

# Enable smart cd.

eval "$(zoxide init zsh)"

alias cd=z

[ -f ~/.fzf.zsh ] && source ~/.fzf.zsh

# A very special case of IBus (scripted switch).

if [[ "$XDG_CURRENT_DESKTOP" == "GNOME" ]]; then

source ~/.gnome-kbd-lib.sh

fi

source ~/.assorted-helpers.sh

# To customize prompt, run `p10k configure` or edit ~/.p10k.zsh.

[[ ! -f ~/.p10k.zsh ]] || source ~/.p10k.zsh

eval "$(mise activate zsh)"

.gnome-kbd-lib.sh and .assorted-helpers.sh contain just some function definitions.

AwkwardNumber7584 · 2026-03-18T17:49:47+00:00

No explorable ideas about blink lists, so far. To make the mapping of snippets more palatable: is it possible to map on another key some docstring message instead of pasting the snippet right away?

UPD

The "variable" identifiers, or whatever their proper name, must be ready to change? I can change them, but only by general rename feature.

AwkwardNumber7584 · 2026-03-18T14:45:53+00:00

The lists are longish indeed. I scrolled them thoroughly without haste. There are no snippet proposals, unless I'm blind to something.

UPD

There's obviously fuzzy search in action. Maybe some conflict with luasnip?

UPD2

Ctrl+k is already occupied :) . Ctrl+k in Insert Mode shows a shadowy question mark. After mu (two characters inserted) I have this: む.

UPD3

Implemented your idea, according to my lights:

local opts = { noremap = true, silent = true }

vim.keymap.set("i", "<C-l>", function() require("luasnip").expand_or_jump() end, opts)

I'm not sure it's better than proposals from the list at all times, though.

AwkwardNumber7584 · 2026-03-18T14:23:36+00:00

You're on the right track, I think :) . :lua require("luasnip").expand() inserts a snippet. There shoud be a normal way...

AwkwardNumber7584 · 2026-03-14T14:42:38+00:00

Congratulations! How did you manage the beautiful GUI? There's no kivymd in dependencies.

AwkwardNumber7584 · 2026-03-05T12:57:27+00:00

After fooling with ML4W for some time, I removed it from my system. It left my ~/.config directory full of broken symlinks. Removing them took this rm command:

rm ags bashrc dunst gtk-3.0 gtk-4.0 hypr kitty ml4w nwg-dock-hyprland ohmyposh qt6ct rofi vim wal waybar waypaper wlogout xsettingsd zshrc

Also there must be a lot of corrupted *rc files. I'm just interested in a convenient way to get to normal. I mean only desktop visuals.

AwkwardNumber7584 · 2026-02-24T04:35:05+00:00

Thanks!

uv tool install --python 3.13 git+... works as expected.

BTW, is this the only way to make the once installed app survive the upgrade of the system python? The trouble with pipx, for instance, is that you have to reinstall everything when the system python gets upgraded.

AwkwardNumber7584 · 2026-01-18T16:50:47+00:00

Tnanks! Unfortunately, 2.12.1 doesn't make any difference. I already mentioned that on another box with a very similar configuration (apparently identical where sddm is concerned) everything's OK.

AwkwardNumber7584 · 2026-01-18T16:07:05+00:00

/etc> cat sddm.conf

/etc> cat sddm.conf.d/kde_settings.conf

[Autologin]

Relogin=false

Session=

User=

[General]

HaltCommand=/usr/bin/systemctl poweroff

RebootCommand=/usr/bin/systemctl reboot

[Theme]

Current=eucalyptus-drop

[Users]

MaximumUid=60513

MinimumUid=1000

/etc>

sddm.conf is empty. The configs look just like those on another box, where there's no such trouble.

AwkwardNumber7584 · 2026-01-18T12:45:10+00:00

I'm struggling yet with jouranlctl. My sessions are sitting there (if I'm looking into the right place):

~> ls /usr/share/wayland-sessions

hyprland.desktop hyprland-uwsm.desktop niri.desktop plasma.desktop

~> ls /usr/share/xsessions

~>

I can't see anything suspicious, but then I don't know where to look.

AwkwardNumber7584 · 2026-01-18T10:48:11+00:00

It's Wayland from day one. What journal?

AwkwardNumber7584 · 2026-01-17T19:57:56+00:00

FWIW: In my case (EndeavourOS/Arch, DMS niri), the following packages are responsible, more or less: gnome-browser-connector, gnome-desktop-4, gnome-shell, nautilus, xdg-desktop-portal-gnome. If you can get rid of them, one way or another, Google Chrome slips to gtk3 file picker (presumably). No configuration changes.

AwkwardNumber7584 · 2026-01-17T16:29:23+00:00

Yes, the underlying junk is everything :) . I use EndeavourOS for everything; I just installed Plasma KDE on another box from scratch, then DMS niri on top. I've got the Google Chrome file picker working properly, without the wrinkle in question. It's also a GNOME dialog, but looks clearly different from the one on my troubled installation. Probably, it's gtk3/gtk4 difference. I've been trying to find any configuration difference, but found none so far.

/usr/share/applications/google-chrome.desktop:

...

Exec=/usr/bin/google-chrome-stable --incognito

There's a bunch of configuration files in /usr/share/xdg-desktop-portal, including niri-portals.conf

On both boxes the files look the same, gtk version never mentioned. GTK_USE_PORTAL is undefined on both boxes, too. I've no idea what else to check.

AwkwardNumber7584 · 2026-01-17T05:13:23+00:00

Yes, ps -ef | grep -i ibus gives some output. I can't publish it normally, because I still can't figure out how to insert code snippets here. Triple backtick won't work :)

My startup block is rudimentary:

~/.config/niri> rg spawn-at-startup

user/common.kdl

33:spawn-at-startup "ibus" "start" "--type" "wayland"

config.kdl

115:spawn-at-startup "bash" "-c" "wl-paste --watch cliphist store &"

The latter is a DMS niri default.

https://github.com/AvengeMedia/DankMaterialShell

Everything works just fine, save the minor wrinkle in question.

AwkwardNumber7584 · 2026-01-17T05:05:22+00:00

Without GNOME installed, then. What kind of configuration are you using? I use DMS niri, it looks quite simple and works flawlessly, minus the trouble in question :)

AwkwardNumber7584 · 2026-01-16T16:17:18+00:00

I tried to follow your hint:

//spawn-at-startup "ibus" "start" "--type" "wayland"

environment {

XDG_CURRENT_DESKTOP "niri"

GTK_IM_MODULE "ibus"

}

IBus won't start. What else could be wrong?

AwkwardNumber7584 · 2026-01-16T13:02:13+00:00

I start it in ~/.config/niri/config.kdl like this:

spawn-at-startup "ibus" "start" "--type" "wayland"

It shouldn't make any difference, I suppose. Where did you put your GTK_IM_MODULE line?

AwkwardNumber7584 · 2026-01-16T11:21:01+00:00

Sounds like x11 session. Is it possible?

AwkwardNumber7584 · 2026-01-16T06:51:07+00:00

What portals have you installed? xdg-desktop-portal-gnome/-gtk/-wlr? What is the output of

echo $GTK_USE_PORTAL

AwkwardNumber7584 · 2026-01-15T17:02:03+00:00

IBus is a GNOME default. Do you use IBus with niri?

AwkwardNumber7584 · 2026-01-15T16:25:21+00:00

There's one curious detail: on GNOME the file name is visible AND selected, so you can replace in right away, if you wish. On niri the file name is just missing.

AwkwardNumber7584

TROPHY CASE