umputun / agterm / 32395976930
94%

DEFAULT BRANCH: master
Ran
Jobs 1
Files 94
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 97.988%. Remained the same
32395976930

push

github

web-flow 
docs: document the macOS Files & Folders permission family (#470)

* docs: document the Files & Folders permission family

The troubleshooting guide covered only the seven entitlement-gated services, and
said that a missing permission means tccd never prompts and agterm never appears
in the matching Privacy pane. Desktop, Documents, Downloads and removable/network
volumes work differently: no entitlement or usage string takes part, the grant is
per app and is never inherited, and it is set under Files & Folders or Full Disk
Access. A user whose listing fails in ~/Downloads read the existing section and
had reason to think he was in the unfixable class.

Also names the diagnostic that separates the two causes: /bin/ls -la answers a
privacy denial with "Operation not permitted" and ordinary permission bits with
"Permission denied", while some ls replacements print the same wording for both.

Related to #468

* docs: correct the usage-string claim and the folder-access diagnostic

macOS does define a usage-description string per protected folder; agterm simply
ships none, so the prompt falls back to Apple's generic wording. Saying no string
takes part reads as "nothing here is agterm's to change", which is wrong in the
one respect that is: WezTerm ships two of these keys and names the terminal in
its prompt.

The diagnostic also had no operand. A privacy denial blocks reading the protected
directory itself, not its entry in the parent, so a bare `/bin/ls -la` run from
home lists Downloads normally and tells the reader nothing.

* docs: replace the absolutes in the Files & Folders section

"The grant is never inherited" contradicted the paragraph below it, which says
Full Disk Access gives every program in a session the same reach. Both were
reaching for one fact: the answer is recorded against the application macOS holds
responsible, so kitty's grant is not agterm's while every command inside agterm
rides on agterm's.

Two other statements were wider tha... (continued)

8083 of 8249 relevant lines covered (97.99%)

4946676.92 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32395976930.1 94
97.99
 GitHub Action Run
Source Files on build 32395976930