Re: [sane-devel] Cannot get hp scanjet 8200 working

2017-01-30 Thread David Niklas
On Tue, 22 Nov 2016 20:54:55 -0800 Dave Platt wrote: > Attached, for your consideration, are three patches I've worked up. > > The first one adds support for a new "option skip-adf" in the > /etc/sane.d/avision.conf file. If you add this option, it should > prevent the

[sane-devel] Cannot get hp scanjet 8200 working

2016-09-02 Thread David Niklas
Hello, I bought an hp scanjet 8200 from amazon and I can't get it to work. Here is a list of commands run and output lightly edited for brevity. Feel free to snip non relevant details. Thanks, in advance. % scanimage --version scanimage (sane-backends) 1.0.24; backend version 1.0.24 % equery l

Re: [sane-devel] Cannot get hp scanjet 8200 working

2016-11-09 Thread David Niklas
On 09/19/2016(Mon) 12:37 "m. allan noah" <kitno...@gmail.com> wrote: > On Sat, Sep 17, 2016 at 7:43 PM, David Niklas <do...@mail.com> wrote: > > I hate to be a pest but it's been two weeks, should I send this > > somewhere else. > > > >> Hello

Re: [sane-devel] Cannot get hp scanjet 8200 working

2016-11-25 Thread David Niklas
On Tue, 11/22/2016 14:16 Dave Platt > >> It seems the avision backend is unmaintained again. You could try > >> upgrading to a more recent version of sane, or one of our git > >> snapshots, that sometimes helps. > >> > >> allan > > > > > > I installed the latest git

Re: [sane-devel] Cannot get hp scanjet 8200 working

2017-03-17 Thread David Niklas
On Mon, 30 Jan 2017 17:02:29 -0800 Dave Platt wrote: > > Sorry for not getting back, I could not get the package manager > > (portage), to accept that I would build the package. > > I ended up creating en ebuild file and manually inserted it into > > the package repository,

Re: [sane-devel] [janitorial] leading whitespace: spaces XOR tabs

2017-08-11 Thread David Niklas
On Wed, 12 Jul 2017 15:35:36 +0200 Gerhard Jäger wrote: > > This whole exercise has made me look at the whole code base in a > > little more detail and, quite frankly, the use of leading whitespace > > is a total and utter mess. Some places are better of than others but > >