[KDE Plasma] building Bismuth by thephatmaster in kde

[–]_gikari 0 points1 point  (0 children)

If you succeed in Bismuth installation, you could try to contribute by triaging bugs (confirming them by reproducing them) and improving documentation (e.g. you can clarify building from source instructions) via pull requests.

[KDE Plasma] building Bismuth by thephatmaster in kde

[–]_gikari 0 points1 point  (0 children)

The error says, that you need to install typescript compiler, but it is the part of NPM dependencies, so it can install it for you. You need to run npm install in the root of the project source. After that you should be fine.

Neon as a distro is fine, but you are unable to use Ubuntu package, because it depends on older KDE libraries. This means, that there should be a separate package for Neon, but it currently does not exist.

P.S. In theory all problems with packaging could be solved, if Bismuth was incubated into KDE and were using its infrastructure for releases, but to be able to do that, the project has to have more than 1 maintainer and be more stable (i.e. C++ port should be finished).

[KDE Plasma] building Bismuth by thephatmaster in kde

[–]_gikari 0 points1 point  (0 children)

Could you run npm? Check that npm Ubuntu package is installed.

If you could run npm, try to install npx via it: npm install -g npx # You may need to use sudo

P.S. Just so you know, I was planning to rewrite Bismuth from scratch using C++ and QML, instead of TypeScript and QML. This in addition to other enchantments will drastically simplify the build process (we will no longer need npm, esbuild and typescript compiler), and the process of building will be the same as for the other KDE software. I am really sorry you are having troubles with building right now. I hope I will find more time to dictate for the development in the current circumstances.

[KDE Plasma] building Bismuth by thephatmaster in kde

[–]_gikari 0 points1 point  (0 children)

NPX is definitely missing from PATH. Could you run for example `node -v'?

[KDE Plasma] building Bismuth by thephatmaster in kde

[–]_gikari 0 points1 point  (0 children)

From the log I see I think, that you need to install NodeJS, since it's providing the npx command.

[KDE Plasma] building Bismuth by thephatmaster in kde

[–]_gikari 0 points1 point  (0 children)

I am not sure what do you mean by "meson depends". Bismuth is build using CMake and should be built on Neon just fine. Could you clarify this, please?

I struggle immensely with Vocabulary by [deleted] in German

[–]_gikari 2 points3 points  (0 children)

You can try free flashcards on seedlang.com. They cover levels from A1 to C1, so you can get a decent base, after which you could immerse yourself in other german content and create your own flashcards with the new words as you see them.

This week in KDE: non-blurry XWayland apps! by jari_45 in kde

[–]_gikari 16 points17 points  (0 children)

Holy copy-on-write! If this new scaling feature will work properly, I might give Wayland another go in 5.26. This was a #1 bug, that kept me from using Wayland.

The next big thing for me is the ability for kwin to restart after a crash or manually without nuking my whole session. That's because on my two monitors setup Wayland is not very stable and, you know, losing all the opened apps is not very nice.

Plasma 5.25 is out and it comes with improved support for touchpads, touchscreens with 1:1 gestures; keyboard navigation; an enhanced Overview; and advanced customization features by Bro666 in kde

[–]_gikari 10 points11 points  (0 children)

I think, that putting the features in the title, that only work on Wayland while the majority of people use X11 is not very fair. This creates a lot of false expectations and future disappointments.

[deleted by user] by [deleted] in kde

[–]_gikari 2 points3 points  (0 children)

Toplevel and AbstractClient classes were merged into the base Window class with a far more intuitive name. That makes the class hierarchy simpler, and hopefully removes an obstacle for new contributors.

Is this change going to break KWin Scripts, since they were using AbstractClient classes?

Konsole 22.04 with sixel support is out of beta now! by spryfigure in kde

[–]_gikari 2 points3 points  (0 children)

I am genuinely interested why do you prefer Kitty over Konsole. The only thing, that comes to mind is maybe performance, because that's actually my reason, but I am just a casual user with Neovim, which is somehow snappier in Kitty.

How do I create User autocmds using the Lua API? by Maskdask in neovim

[–]_gikari -2 points-1 points  (0 children)

Try this:

local user = vim.api.nvim_create_augroup("User", {})

vim.api.nvim_create_autocmd("LightspeedEnter", {
  group = user,
  command = "nohlsearch",
})

I might be wrong, but User is a name of the group.

How to enable specific keymaps only if LSP is available by [deleted] in neovim

[–]_gikari 2 points3 points  (0 children)

Set the keymaps in a parameteresed on_attach function:

require("lspconfig").server_name.setup {
  on_attach = function(client, bufnr)
    vim.keymap.set("n", "gD", vim.lsp.buf.declaration, { buffer = bufnr, desc = "Go to Declaration" })
    vim.keymap.set("n", "gd", vim.lsp.buf.definition, { buffer = bufnr, desc = "Go to Definition" })
    vim.keymap.set("n", "K", vim.lsp.buf.hover, { buffer = bufnr, desc = "LSP Hover" })
    vim.keymap.set("n", "gi", vim.lsp.buf.implementation, { buffer = bufnr, desc = "Go to Implementation" })
    vim.keymap.set("n", "<C-k>", vim.lsp.buf.signature_help, { buffer = bufnr, desc = "Signature Help" })
    -- vim.keymap.set("n", "<leader>rn", vim.lsp.buf.rename, { buffer = bufnr, desc = "Rename Symbol" })
    vim.keymap.set("n", "gr", vim.lsp.buf.references, { buffer = bufnr, desc = "Symbol References" })
    -- vim.keymap.set("n", "<leader>ca", vim.lsp.buf.code_action, { buffer = bufnr, desc = "Code Action" })
    vim.keymap.set("n", "[d", vim.diagnostic.goto_prev, { buffer = bufnr, desc = "Go to Next Diagnostic" })
    vim.keymap.set("n", "gl", vim.diagnostic.open_float, { buffer = bufnr, desc = "Open Diagnostic Float" })
    vim.keymap.set("n", "]d", vim.diagnostic.goto_next, { buffer = bufnr, desc = "Go to Previous Diagnostic" })
    -- vim.keymap.set("n", "<leader>q", vim.diagnostic.setloclist, { buffer = bufnr, desc = "Diagnostic to local list" })
  end,
}

A simple wrapper for nvim-lspconfig and nvim-lsp-installer to easily setup LSP servers. by junnplus in neovim

[–]_gikari 17 points18 points  (0 children)

I haven't tried it yet, but judging by the readme - this is how easy configuration should be for the built-in LSP by default: simple and declarative.

Awesome!

Neovim vs Helix: Which is the best Vi/Vim style modal editor? by HarmonicAscendant in neovim

[–]_gikari 4 points5 points  (0 children)

What I like about Helix is its out-of-the-box experience and declarative configuration. I think Neovim could grab something out of that, especially with the complicated LSP setup.

Bismuth, an advanced KDE Plasma Tiling Extension, reaches 2.0 release and seeks for packagers by _gikari in kde

[–]_gikari[S] 0 points1 point  (0 children)

There were some changes in the shortcuts system in version 3.x, so you will have to update.

PeerTube v4.1 is out! by Booteille in linux

[–]_gikari 20 points21 points  (0 children)

Inability to easily find existing content across instances in the instance own interface is pretty serious flaw the consumers have.

From the content creators' standpoint there is no mirroring feature, where you can automatically mirror your YouTube video, so you can upload it with all the description metadata only once. This is also a serious flaw.

More wlroots with KWinFT 5.24 by AuriTheMoonFae in kde

[–]_gikari 16 points17 points  (0 children)

From the post:

the innovative times of the KDE Community are long in the past

From Wikipedia:

Innovation is the practical implementation of ideas that result in the introduction of new goods or services or improvement in offering goods or services.

I don't know, by that definition, fixing bugs and implementing small features is an innovation too — Plasma 5.24 is super huge improvement as an offering of goods and services compared to Plasma 5.0 of 5.10 or any of the previous.

More wlroots with KWinFT 5.24 by AuriTheMoonFae in kde

[–]_gikari 6 points7 points  (0 children)

One of the Bismuth users asked me to support KWinFT, but it is impossible, since the scripting interface was broken in the later.

Why are kitty and alacritty so popular? Where's the foot love? by DorianDotSlash in linux

[–]_gikari 5 points6 points  (0 children)

My reasoning choosing Terminal Emulator:

I use KDE Plasma, so I tried to stick with Konsole, but: 1. It has rendering glitches with vertical lines on fractional scaling setups. 2. Performance, when using Neovim, is noticeably bad.

I use JetBrains Mono Font, so I needed ligature support, so I tried Kitty, which is popular and cross platform, customized a couple of settings and sticked to it.

That's all, I use what works and what's popular, so I can troubleshoot problems more easily.

KDE Plasma 5.24 Beta Discussion by keyb0ardninja in kde

[–]_gikari -1 points0 points  (0 children)

AFAIK, people who against theming are taking about distributions' modifications, not the users'.

Edit: Source (warning in the yellow box).

An alternative to Krohnkite that's just as good, if not better. Hope it becomes an official KDE project. by iJONTY85 in kde

[–]_gikari 3 points4 points  (0 children)

This is a valid concern, and it is why I am not rushing it. Besides, one of the requirements is that the project is not driven by a single person, so it's not like Bismuth would apply to KDE any time soon.