Ross Jacobs

Results 36 comments of Ross Jacobs

I wanted to isolate this issue, so ;es is the only trigger. ![image](https://user-images.githubusercontent.com/10995145/144544096-98750b4c-d90d-4330-84d8-97ef968c9e93.png) For some reason macos won't let me toggle it off/on. ![image](https://user-images.githubusercontent.com/10995145/144544133-940c1e2d-ef96-4724-b3d9-cc520ad05f5a.png)

I have done as you've asked. It seems that espanso on 12.0.1 isn't detecting whether it has the accessibility access that it needs, because when double-clicking on the app, it...

So I deleted all of my espanso yml files, and now it works. There's a weird behavior that I've noticed. It seems like my problem is related to the trigger...

This is reproducible 1. Delete all espanso files 2. `espanso restart` 3. `espanso edit`, add the above config 4. After saving, type `;es` (nothing happens) 5. Type `:espanso` => expands...

I appreciate the effort that you've put into the new version. I am still seeing this issue though on most recent v2.2.0 on macos. https://user-images.githubusercontent.com/10995145/104255735-93cf5780-542e-11eb-8adb-d4e3345121d1.mov

What kind of functionality are you expecting?

Why not use [this converter](https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/converting-etl-files-to-pcap-files/ba-p/1133297) and then read the resulting pcap? Unixy tools are "supposed" to do one thing well, and termshark would likely call that tool anyway.

Changing title to increasing code coverage. Currently, it looks like code coverage is 23%. ```bash bash-5.0$ go test -coverprofile=c.out ./termshark ok _/Users/rj/code/termshark 0.303s coverage: 23.2% of statements ```