Ricardo Wurmus transcribed 0.9K bytes: > > ng0 writes: > > > Without this patch, alpine silently(?) complains until a > > $HOME/.pinerc exists: > > How does it complain “silently”? :) I removed my .pinerc symlink and this is what happens. I should've described the problem before I sent this: Upon first start, a .pinerc is generated from a global file[1], but we also get a ".pine-debug1" and with every start a new one this with a number increase. Is it just because of these files? I'm not a alpine user.. This .pine-debug1 is appended. Twice because I forgot how to remove attachments. 1: I _guess_ ... the existing file is actually not existing so I don't know what alpine does here. Fixing it the way I did it seemed like the first possible solution to me. > > The way they are created is copied from slackware and seems to be > > the recommended way of providing them, as no such file exists in > > the distribution of alpine. > > Recommended by whom? I see in the manual [1] that Actually this is a comment in a file I can longer find (slackbuilds?) which came up when I searched for this problem. > $prefix/lib/pine.conf (Pine's global configuration file) > $prefix/lib/pine.conf.fixed (Non-overridable global configuration file) > > should exist, but it doesn’t say what should be in them. Could they > just be empty? Given that one of them is for non-overridable global > configurations I’d rather not fill them. > > [1]: https://www.washington.edu/alpine/tech-notes/installation.html#files-unix ^ Keep in mind that this |-- is not the alpine we use. If it is > WDYT? > > -- > Ricardo > > GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC > https://elephly.net > > -- ng0 OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588