Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In a PKGBUILD file b2sums, cksums and architectures are not highlighted #1235

Open
Alleop5 opened this issue Feb 28, 2025 · 1 comment
Open

Comments

@Alleop5
Copy link

Alleop5 commented Feb 28, 2025

Problem

Source: https://man.archlinux.org/man/core/pacman/PKGBUILD.5.en

In the list below there should be b2sums and cksums.

lex:add_rule('constant', token(lexer.CONSTANT, word_match{
-- We do *not* list pkgver srcdir and startdir here.
-- These are defined by makepkg but user should not alter them.
'arch', 'backup', 'changelog', 'checkdepends', 'conflicts', 'depends', 'epoch', 'groups',
'install', 'license', 'makedepends', 'md5sums', 'noextract', 'optdepends', 'options', 'pkgbase',
'pkgdesc', 'pkgname', 'pkgrel', 'pkgver', 'provides', 'replaces', 'sha1sums', 'sha256sums',
'sha384sums', 'sha512sums', 'source', 'url', 'validpgpkeys'
}))

But you can also put an architecture after if you add an underscore. I'm pretty sure any architecture is valid for expandability so depends_insertfuturearchitecturehere is also valid.
Here's the list of them: source, depends, makedepends, checkdepends, optdepends, conflicts, provides, replaces, cksums, md5sums, sha1sums, sha224sums, sha256sums, sha384sums, sha512sums, b2sums.

Steps to reproduce

No response

vis version (vis -v)

vis 0.9 +curses +lua +tre +acl

Terminal name/version

No response

$TERM environment variable

No response

@ninewise
Copy link
Collaborator

ninewise commented Mar 1, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants