git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: meson: Installing completions

From
AHAkshay Hegde <lists+git@akshay.is>
Date
Apr 1, 2025, 17:43 UTC
Message-ID
<Z-wltqWraESmb-Lm@akshay.is>
In-Reply-To
<Z-u42Sm613hMj1Ft@pks.im>
On 2025-04-01 11:58 +0200, Patrick Steinhardt wrote:
Show 8 quoted lines
>> I just wanted to double check if I'm supposed to install them manually,
>> or if I missed enabling some options (I looked through the top-level
>> meson_options.txt and meson.build files and I don't think I did.)
>
>For now the status quo is that you have to install them manually, which
>indeed isn't optimal. It matches our Makefile, which never installed
>those completions, either. But that by itself isn't a good enough
>argument from my perspective that it needs to be the same with Meson.

Yup that seems entirely reasonable to me, and this was my initial thought. I don't have much of an issue installing them manually.

Show 8 quoted lines
>
>The biggest question though is whether distros are aligned enough for us
>to provide standard installation paths. That is, do all distros end up
>installing bash completion into "/usr/share/bash-completion"? What are
>the desired directories for tcsh and zsh completion?
>
>If there is enough standardization then yes, I totally think we should
>start installing completion scripts automatically.

Well I can't speak from any sort of authoritativeness here, but for zsh, they are usually installed underneath the datadir (usually /usr/share), then under zsh/site-functions. Of course, I don't know if that's true for all distros.

Could we extend meson_options to allow specification of bash/tcsh/zsh completion directories? If they are not empty, I think it would be reasonable to have meson install it automatically.

Either way, I personally don't think it's too big a deal but would be a good 'quality-of-life' improvement.

Cheers,
-- 
	Akshay
Previous: Patrick SteinhardtNext: Todd Zullinger
Message 3 of 7 in “meson: Installing completions”
  1. Akshay HegdeApr 1, 2025
  2. Patrick SteinhardtApr 1, 2025
  3. Akshay HegdeApr 1, 2025
  4. Todd ZullingerApr 2, 2025
  5. Patrick SteinhardtApr 2, 2025
  6. Todd ZullingerApr 2, 2025
  7. Patrick SteinhardtApr 7, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.