On Wed, Apr 16 2014, Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote:
> On 04/16/2014 05:48 PM, Jameson Graef Rollins wrote:
>> I actually don't want the spawned process to be owned by xapers.  If
>> it's owned by xapers then closing xapers closes the opened paper.
>> That's why I used the technique that I did.
>
> hm, that doesn't happen for me (i just tested).   can you provide a
> workflow that makes that happen?  here's what i did:
>
>  * xapers add --file=blah.pdf --tags=test
>  * xapers view test
>  * hit enter when blah.pdf is selected
>  * leave the pdf viewer open (i've tried with okular and evince), and
> back in the xapers view console, hit q
>  * xapers terminates, pdf viewer remains open.

Ok, this actually sounds fine then.  If the viewer remains open even
after xapers has closed, then this looks like a good solution.

> looking at my test changes, i see that maybe you do want to send stderr
> and stdout to /dev/null, which i probably shouldn't have stripped.  i'll
> try to re-add that, and send the patches to the list.

That would be great.  I'll test the new patch and try to roll out a new
version soon.

>> Another possible way to deal with this issue is that xapers could always
>> rewrite the file name when importing papers.  Currently it's keeping the
>> name of the file when importing, but it doesn't have to.  It could write
>> it's own file name, and not worry about whatever was user supplied.
>
> would xapers remember the original filename? for some people (and some
> papers) that might be a useful piece of information.

That's why I left the name as is.  I honestly haven't come across a
legit reason to save the name, though, which is why I'm tempted to just
rename.  If people think there's a reason to keep the name as is then we
can just continue to do that.

jamie.

Attachment: pgp2xQxd9xku4.pgp
Description: PGP signature

Reply via email to