Arch IRC channels (Français)
Cette page ne traite que des canaux IRC de la communauté francophone. Pour le reste consultez Arch IRC channels.
Remarques
Le canal officiel de la communauté archlinux.fr est #archlinux-fr sur le réseau libera.chat ( #archlinux-fr@irc.libera.chat ). Les archives de discussion de ce canal sont disponibles.
En plus de fournir une aide plus directe grâce aux participants, la communauté met à disposition un bot arch_ange offrant certaines fonctionnalités pour les utilisateurs.
Astuce: La lecture de ce texte sur la manière de poser les questions d'une manière intelligente et son application sont conseillées.
arch_ange
Le bot répond à toute commande connue préfixée par ! :
- wikiorg
- recherche sur le wiki anglophone.
- pkg
- recherche d'un paquet.
- desc
- description d'un paquet (éventuellement sur AUR).
- pkgfile
- recherche d'un paquet contenant un fichier.
- aur
- recherche d'un paquet sur AUR.
Recherche sur le wiki
wiki terme [> nick]
- terme
- correspond au contenu de la recherche.
- nick
- (optionnel) est un pseudo actuellement présent sur le canal, arch_ange lui adressera la réponse.
Exemple :
<tuxce> !wikiorg xorg <arch_ange> tuxce: https://wiki.archlinux.org/Xorgdead+link+2022-09-17 ⓘ
Recherche d'un paquet
pkg terme
terme
- correspond au contenu de la recherche.
La recherche limite à 5 le nombre de résultats.
Exemples :
<nheir> !pkg linux <arch_ange> core/linux 4.5.2-1 The Linux kernel and modules <arch_ange> core/syslinux 6.03-6 Collection of boot loaders that boot from FAT, ext2/3/4 and btrfs filesystems, from CDs and via PXE <arch_ange> extra/ibus 1.5.13-2 Next Generation Input Bus for Linux <arch_ange> extra/libva 1.7.0-1 Video Acceleration (VA) API for Linux <arch_ange> extra/lirc 1:0.9.3.a-2 Linux Infrared Remote Control utils
Description d'un paquet
desc paquet [> nick]
- paquet
- correspond nom du paquet.
- nick
- (optionnel) est un pseudo actuellement présent sur le canal, arch_ange lui adressera la réponse.
La recherche bascule sur AUR si le paquet n'est pas dans les dépôts.
Exemples :
<nheir> !pkg linux <arch_ange> nheir: core/linux 4.5.2-1 The Linux kernel and modules
Recherche d'un paquet contenant un fichier
pkgfile path
path
- correspond au contenu de la recherche, l'utilisation des expressions régulières n'est pas permise.
Exemple :
<nheir> !pkgfile gnome-session <arch_ange> extra / gnome-session 3.20.1-1 usr/bin/gnome-session
Recherche d'un paquet sur AUR
aur terme
terme
- correspond au contenu de la recherche.
La recherche limite à 5 le nombre de résultats.
Exemple :
<nheir> !aur supybot <arch_ange> aur/supybot-git 0.83.4.1.7089.6f925e5-1 A cross-platform IRC bot written in Python supybot-gitAUR <arch_ange> aur/limnoria-git 0.83.4.1.10347.530c246-1 An IRC bot based on Supybot, with sqlite3 support and other features (dev channel) limnoria-gitAUR
gollark: Oh, and it's not a special case as much as just annoying, but it's a compile error to not use a variable or import. Which I would find reasonable as a linter rule, but it makes quickly editing and testing bits of code more annoying.
gollark: As well as having special casing for stuff, it often is just pointlessly hostile to abstracting anything:- lol no generics- you literally cannot define a well-typed `min`/`max` function (like Lua has). Unless you do something weird like... implement an interface for that on all the builtin number types, and I don't know if it would let you do that.- no map/filter/reduce stuff- `if err != nil { return err }`- the recommended way to map over an array in parallel, if I remember right, is to run a goroutine for every element which does whatever task you want then adds the result to a shared "output" array, and use a WaitGroup thingy to wait for all the goroutines. This is a lot of boilerplate.
gollark: It also does have the whole "anything which implements the right functions implements an interface" thing, which seems very horrible to me as a random change somewhere could cause compile errors with no good explanation.
gollark: - `make`/`new` are basically magic- `range` is magic too - what it does depends on the number of return values you use, or something. Also, IIRC user-defined types can't implement it- Generics are available for all of, what, three builtin types? Maps, slices and channels, if I remember right.- `select` also only works with the built-in channels- Constants: they can only be something like four types, and what even is `iota` doing- The multiple return values can't be used as tuples or anything. You can, as far as I'm aware, only return two (or, well, more than one) things at once, or bind two returns to two variables, nothing else.- no operator overloading- it *kind of* has exceptions (panic/recover), presumably because they realized not having any would be very annoying, but they're not very usable- whether reading from a channel is blocking also depends how many return values you use because of course
gollark: What, you mean no it doesn't have weird special cases everywhere?
This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.