Prathamesh Mahaleanddanielwerg 80192ab1cb feat(lua): add lua-language-server type stubs for the yay global (#2884)
* feat(lua): add lua-language-server type stubs for the yay global

Ship a meta/yay.meta.lua definition file that declares the `yay` global,
all yay.opt fields, and every autocmd event payload so lua-language-server
users get completion, hover docs, and typo detection without an
"Undefined global `yay`" warning.

- meta/yay.meta.lua: 232-line stub covering opt (45 fields), log, abort,
  create_autocmd with per-event overloads, and 14 payload classes for the
  5 autocmd events (AURPreInstall, AURPostDownload, UpgradeSelect,
  PostInstall, SearchFilter). Return contracts for UpgradeSelect and
  SearchFilter are annotated.
- doc/lua.md: add "Editor support" section with .luarc.json setup.
- doc/init.lua: fix PostInstall example referencing pkg.installed, a
  field that does not exist on PostInstallPackage.
- Makefile: install/uninstall meta/yay.meta.lua to
  $(PREFIX)/share/yay/meta/ so the documented /usr/share/yay/meta path
  exists on installed systems.

Closes #2876

* doc(lua): fix api-since version to v13.0.1

* feat(lua): apply review feedback on type stubs

Type opt fields as string unions with descriptions, rename to yay.d.lua
per LuaLS docs, strip redundant comments from doc/init.lua, bump to v13.0.2.

Tested everything again: go build, go test, lua-language-server, gendocs.

* doc(lua): move "editor support", add hyperlinks

added link to `init.lua` example in "location" paragraph

having "editor support" paragraph at the very bottom of document didn't make any sense. user would want to have lsp editor support right after creating a file in config dir if ever.

removed useless paragraph about `.luarc.json` location that already been explained aboved.

added hyperlinks for luals extensions. couldn't find any special info for helix (unlike jetbrains), but it should be already covered by "other editors"

---------

Co-authored-by: danielwerg <35052399+danielwerg@users.noreply.github.com>
2026-06-24 00:28:28 +02:00
2020-07-20 09:27:25 +02:00
2016-09-05 03:43:29 +01:00

yay yay-bin yay-git AUR votes GitHub license

yay

Yet Another Yogurt - An AUR Helper Written in Go

Help translate yay: Transifex

Features

  • Advanced dependency solving
  • PKGBUILD downloading from ABS or AUR
  • Completions for AUR packages
  • Query user up-front for all input (prior to starting builds)
  • Narrow search (yay linux header will first search linux and then narrow on header)
  • Find matching package providers during search and allow selection
  • Remove make dependencies at the end of the build process
  • Build local PKGBUILDs with AUR dependencies
  • Un/Vote for packages

asciicast

asciicast

Installation

If you are migrating from another AUR helper, you can simply install yay with that helper.

Warning

We are using sudo in these examples. You can switch that out for a different privilege escalation tool.

Source

The initial installation of yay can be done by cloning the PKGBUILD and building with makepkg:

We make sure we have the base-devel package group installed.

sudo pacman -S --needed git base-devel
git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si

If you want to do all of this at once, we can chain the commands like so:

sudo pacman -S --needed git base-devel && git clone https://aur.archlinux.org/yay.git && cd yay && makepkg -si

Binary

If you do not want to compile yay yourself you can use the builds generated by GitHub Actions.

sudo pacman -S --needed git base-devel
git clone https://aur.archlinux.org/yay-bin.git
cd yay-bin
makepkg -si

If you want to do all of this at once, we can chain the commands like so:

sudo pacman -S --needed git base-devel && git clone https://aur.archlinux.org/yay-bin.git && cd yay-bin && makepkg -si

Other distributions

If you're using Manjaro or another distribution that packages yay you can simply install yay using pacman (as root):

pacman -S --needed git base-devel yay

Warning

distributions sometimes lag updating yay on their repositories.

First Use

Development packages upgrade

  • Use yay -Y --gendb to generate a development package database for *-git packages that were installed without yay. This command should only be run once.

  • yay -Syu --devel will then check for development package updates

  • Use yay -Y --devel --save to make development package updates permanently enabled (yay and yay -Syu will then always check dev packages)

Examples of Custom Operations

Command Description
yay Alias to yay -Syu.
yay <Search Term> Present package-installation selection menu.
yay -Bi <dir> Install dependencies and build a local PKGBUILD.
yay -G <AUR Package> Download PKGBUILD from ABS or AUR. (yay v12.0+)
yay -Gp <AUR Package> Print to stdout PKGBUILD from ABS or AUR.
yay -Ps Print system statistics.
yay -Syu --devel Perform system upgrade, but also check for development package updates.
yay -Wu <AUR Package> Unvote for package (Requires setting AUR_USERNAME and AUR_PASSWORD environment variables) (yay v11.3+)
yay -Wv <AUR Package> Vote for package (Requires setting AUR_USERNAME and AUR_PASSWORD environment variables). (yay v11.3+)
yay -Y --combinedupgrade --save Make combined upgrade the default mode.
yay -Y --gendb Generate development package database used for devel update.
yay -Yc Clean unneeded dependencies.

Frequently Asked Questions

  • yay does not display colored output. How do I fix it?

    Make sure you have the Color option in your /etc/pacman.conf (see issue #123).

  • Sometimes diffs are printed to the terminal, and other times they are paged via less. How do I fix this?

    yay uses git diff to display diffs, which by default tells less not to page if the output can fit into one terminal length. This behavior can be overridden by exporting your own flags (export LESS=SRX).

  • yay is not asking me to edit PKGBUILDS, and I don't like the diff menu! What can I do?

    yay --editmenu --diffmenu=false --save

  • How can I tell yay to act only on AUR packages, or only on repo packages?

    yay -{OPERATION} --aur yay -{OPERATION} --repo

  • A Flagged Out Of Date AUR Packages message is displayed. Why doesn't yay update them?

    This message does not mean that updated AUR packages are available. It means the packages have been flagged out of date on the AUR, but their maintainers have not yet updated the PKGBUILDs (see outdated AUR packages).

  • yay doesn't install dependencies added to a PKGBUILD during installation.

    yay resolves all dependencies ahead of time. You are free to edit the PKGBUILD in any way, but any problems you cause are your own and should not be reported unless they can be reproduced with the original PKGBUILD.

  • I know my -git package has updates but yay doesn't offer to update it

    yay uses a hash cache for development packages. Normally it is updated at the end of the package install with the message Found git repo. If you transition between aur helpers and did not install the devel package using yay at some point, it is possible it never got added to the cache. yay -Y --gendb will fix the current version of every devel package and start checking from there.

  • I want to help out!

    Check CONTRIBUTING.md for more information.

Support

All support related to yay should be requested via GitHub issues. Since yay is not officially supported by Arch Linux, support should not be sought out on the forums, AUR comments or other official channels.

A broken AUR package should be reported as a comment on the package's AUR page. A package may only be considered broken if it fails to build with makepkg.

Reports should be made using makepkg and include the full output as well as any other relevant information. Never make reports using yay or any other external tools.

Images

Other AUR helpers/tools

S
Description
No description provided
Readme GPL-3.0
21 MiB
0 Stars 1 Watchers 0 Forks
Languages
Go 94%
Shell 4.4%
Lua 1%
Makefile 0.4%
Dockerfile 0.2%