Am 08.09.2016 um 08:44 schrieb Matthias Urlichs:
> On 08.09.2016 08:29, Johan Ström wrote:
>> Regardless of which one we find most
>> suiting, I'd say we should keep all info in *one* place
> Personally I'd rather use Sphinx or similar. The main reason is that
> it's reasonably easy to sustain a co
On 7 September 2016 at 23:03, Jan Kandziora wrote:
> ...
> In reality, we don't need this "simple" markup when all the people who
> are contributing to the documentation are developers.
Not necessarily true. I have recently been guided on this list as to
how to interface 1-wire devices to a Raspb
Am 08.09.2016 um 09:58 schrieb Colin Law:
> On 7 September 2016 at 23:03, Jan Kandziora wrote:
>> ...
>> In reality, we don't need this "simple" markup when all the people who
>> are contributing to the documentation are developers.
>
> Not necessarily true. I have recently been guided on this li
On 8 September 2016 at 09:20, Jan Kandziora wrote:
> Am 08.09.2016 um 09:58 schrieb Colin Law:
>> On 7 September 2016 at 23:03, Jan Kandziora wrote:
>>> ...
>>> In reality, we don't need this "simple" markup when all the people who
>>> are contributing to the documentation are developers.
>>
>> N
> On 08 Sep 2016, at 10:20, Jan Kandziora wrote:
>
> Face it, simple markup alone will not give you any contributors. Hell,
> non-developer documentation contributors don't want to bother with
> markup at all!
>
> What we need is an interface that makes it easy for *anyone* to
> contribute to t
> On Sep 8, 2016, at 2:53 AM, Stefano Miccoli wrote:
>
>
>> On 08 Sep 2016, at 10:20, Jan Kandziora wrote:
>>
>> Face it, simple markup alone will not give you any contributors. Hell,
>> non-developer documentation contributors don't want to bother with
>> markup at all!
>>
>> What we need
Am 08.09.2016 um 11:52 schrieb Colin Law:
>>
>> Face it, simple markup alone will not give you any contributors. Hell,
>> non-developer documentation contributors don't want to bother with
>> markup at all!
>
> Wikipedia doesn't seem to have problems getting contributors.
>
Oh, COME ON. At Wikipe
From the python point of view it’s OK…
I think it’s an owserver bug (or feature, I do not know ;-) since I have your
very same behaviour.
S
> On 08 Sep 2016, at 00:03, Mick Sulley wrote:
>
> Stefano,
> I took your ex.py and modified it slightly to use a variable as the base
> device name -
Well it's reassuring to know that it is not just me :)
I have been testing some more and with multiple devices it seems to
rename some and then fail part way through. I have code that list all
of the devices, the fields and their values. If I run that after a
rename failure that fails as well
First of, I agree that writing all content in HTML, even if ever so
basic HTML, is tedious when I just want to write text. Having to write
italic instead of just *italic* does become quite tiresome in the
long run..
Also, I don't want to be forced to click buttons to make my text bold,
or to w
I just picked up a DS2482S-100 based i2c to 1-wire bridge (this one:
https://www.modmypi.com/raspberry-pi/breakout-boards/owfs-1-wire/r-pi-i2c-1-wire-owfs-expansion-module-
) that I want to use with my R-Pi 2.
The product site has detailed instructions for setting up OWFS under
Raspbian Wheezy, wh
Am 08.09.2016 um 22:38 schrieb Juliean Galak:
> I'd like to use a newer Raspbian distro (Jessie, Kernel 4.4) and am
> wondering if just installing OWFS with apt-get will do the trick. Are the
> drivers needed for this in place?
>
If you don't use the w1 drivers, yes. But it is rather old,
so you s
Thank you.
I no longer need to use w1, so i2c only is fine and seems easier to use.
With only a bit of tweaking (mostly just using "server: i2c=ALL:ALL") those
instructions worked perfectly. Thank you!
Juliean.
On Thu, Sep 8, 2016 at 8:37 PM, Jan Kandziora wrote:
> Am 08.09.2016 um 22:38 sch
13 matches
Mail list logo
