You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe I have spotted an error or inconsistency on the Wiki page. From the doc I can read:
"To get basic aliasing, simply put a pueue_aliases.yml besides your pueue.yml."
However, even though I have pueue_aliases.yml in my ~/.config/pueue/ with pueue.yml, service tries to read aliases from config folder.
logs:
"Didn't find pueue alias file at "/home/miro/.config/pueue_aliases.yml"."
Adding --config parameter doesn't give that message but also doesn't fix this issue.
Location /home/miro/pueue_aliases.yml fix that, but it can confuse the users.
Steps to reproduce
Put pueue_aliases.yml in my ~/.config/pueue/ with pueue.yml
Add aliases from the wiki example.
Run pueue add -- ls
Debug logs (if relevant)
Didn't find pueue alias file at "/home/miro/.config/pueue_aliases.yml".
Operating system
Manjaro
Pueue version
v3.3.1
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
I believe I have spotted an error or inconsistency on the Wiki page. From the doc I can read:
"To get basic aliasing, simply put a pueue_aliases.yml besides your pueue.yml."
However, even though I have
pueue_aliases.yml
in my~/.config/pueue/
withpueue.yml
, service tries to read aliases fromconfig
folder.logs:
"Didn't find pueue alias file at "/home/miro/.config/pueue_aliases.yml"."
Adding
--config
parameter doesn't give that message but also doesn't fix this issue.Location
/home/miro/pueue_aliases.yml
fix that, but it can confuse the users.Steps to reproduce
Put
pueue_aliases.yml
in my~/.config/pueue/
withpueue.yml
Add aliases from the wiki example.
Run
pueue add -- ls
Debug logs (if relevant)
Didn't find pueue alias file at "/home/miro/.config/pueue_aliases.yml".
Operating system
Manjaro
Pueue version
v3.3.1
Additional context
No response
The text was updated successfully, but these errors were encountered: