Skip to content

Update escape, repeat, snipbank to 1.0.2#231

Closed
dicksonlaw583 wants to merge 1 commit into
espanso:mainfrom
dicksonlaw583:main
Closed

Update escape, repeat, snipbank to 1.0.2#231
dicksonlaw583 wants to merge 1 commit into
espanso:mainfrom
dicksonlaw583:main

Conversation

@dicksonlaw583

Copy link
Copy Markdown
Contributor

I would like to update my Escape, Repeat, and Snipbank to 1.0.2 to resolve an issue with missing _pkgsource.yml files causing espanso package commands to fail.

See initial release: #188

@smeech

smeech commented Jul 5, 2026

Copy link
Copy Markdown
Collaborator

I would like to update my Escape, Repeat, and Snipbank to 1.0.2 to resolve an issue with missing _pkgsource.yml files causing espanso package commands to fail.

See initial release: #188

I wasn't aware of any problems with espanso package install commands for your packages, and have just rechecked that they work. We don't normally include _pkgsource.yml files. Did you make any other changes? The way Federico preferred to keep old versions of packages makes it difficult to compare them with new ones!

@dicksonlaw583

Copy link
Copy Markdown
Contributor Author

@smeech

If _manifest.yml is present but _pkgsource.yml is not, running any espanso package commands (e.g. espanso package list) will result in the following error:

unable to list packages: unable to list packages

Caused by:
    0: unable to parse package source file
    1: No such file or directory (os error 2)

I also learned of this fairly recently, which I am now correcting across all packages published under my name.

@smeech

smeech commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

I think you have something else going on, I'm afraid. _pkgsource.yml isn't required for Espanso packages, and apart from one, none of them have such a file.

It's possible your problems with espanso package commands might be due to having manually added a package to your espanso/match/packages directory - perhaps one of your own? I would suggest moving the contents of the folder elsewhere to see if that resolves the problem, and then re-load the packages you use with Espanso commands.

@dicksonlaw583

Copy link
Copy Markdown
Contributor Author

@smeech

I have added some custom legacy packages to my installation, but removing them doesn't change anything. The unable to list packages: unable to list packages error only appears when there is an installed package that contains a _manifest.yml file but no _pkgsource.yml, which is the main motivation behind the patch.

For the information, I am running Espanso 2.3.0 on Mac OS.

@smeech

smeech commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

The _pkgsource.yml file is normally created during the espanso package install process. You appear to have found a way around a corrupted package index! I wish I had known that when I encountered a similar problem and had to follow a process like I described above.

In any event, your packages are fine as they are, and don't need _pkgsource.yml files.

Thank you, nevertheless.

@smeech smeech closed this Jul 7, 2026
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

Successfully merging this pull request may close these issues.

2 participants