To James; if you would like a reply to an offline email, please use an
accessible email address. The last time I tried to reply, my message bounced.
—
p...@ehealth.id.au
“…you refuse to come to me that you may have life.”
Thanks, Richard, for the history lesson.
peter
—
p...@ehealth.id.au
“…an hour is coming when all who are in the tombs will hear his voice and come
out…”
> On 18 Mar 2021, at 2:50 am, Richard L. Hamilton wrote:
>
> I think you may be mixing apples and oranges.
>
> As I recall, the ability to
I think you may be mixing apples and oranges.
As I recall, the ability to literally use read() began in very early Unix, when
only one filesystem type existed (before SVR3 FSS or BSD VFS mechanisms that
allowed multiple filesystem implementations). The original type had 16-byte
entries, with
Argh! I was wrong.
$ cat /tmp
cat: /tmp: Is a directory
Sorry for the noise.
> Am 17.03.2021 um 16:19 schrieb Christoph Kukulies :
>
> There was some discussion in the FreeBSD mailing list about changing the
> behaviour of a directory fd WRT
> the read() function. A change has been made
There was some discussion in the FreeBSD mailing list about changing the
behaviour of a directory fd WRT
the read() function. A change has been made towards disallowing this from
FreeBSD 12.2 onwards (IIRC) and there was big discussion on this since it
„violates“ the cleanness of UNIX, that a
> On Mar 17, 2021, at 07:47, joerg van den hoff wrote:
>
>
>
> On 17.03.21 13:16, Ryan Schmidt wrote:
>> On Mar 17, 2021, at 07:04, joerg van den hoff wrote:
>>> and sadly even `sudo port -ns upgrade --force meld)' does not solve the
>>> problem...
>>>
>>> too bad. but I appreciate your
On 17.03.21 13:16, Ryan Schmidt wrote:
On Mar 17, 2021, at 07:04, joerg van den hoff wrote:
and sadly even `sudo port -ns upgrade --force meld)' does not solve the
problem...
too bad. but I appreciate your help. at least I now understand where
approximately the problem is located ...
On Mar 17, 2021, at 07:04, joerg van den hoff wrote:
> and sadly even `sudo port -ns upgrade --force meld)' does not solve the
> problem...
>
> too bad. but I appreciate your help. at least I now understand where
> approximately the problem is located ...
According to
On 17.03.21 12:39, Ryan Schmidt wrote:
> On Mar 17, 2021, at 06:36, joerg van den hoff wrote:
>> On 17.03.21 11:07, Ryan Schmidt wrote:
>>> I think there is something wrong with your /opt/local/share/gir-1.0/GtkSource-4.gir.
Specifically in mine, there is the line:
>>>
On Mar 17, 2021, at 06:36, joerg van den hoff wrote:
> On 17.03.21 11:07, Ryan Schmidt wrote:
>> I think there is something wrong with your
>> /opt/local/share/gir-1.0/GtkSource-4.gir. Specifically in mine, there is the
>> line:
>> shared-library="/opt/local/lib/libgtksourceview-4.0.dylib"
>>
On 17.03.21 11:07, Ryan Schmidt wrote:
On Mar 17, 2021, at 04:07, joerg van den hoff wrote:
On 17.03.21 05:07, Ryan Schmidt wrote:
On Mar 16, 2021, at 13:47, joerg van den hoff wrote:
"** (meld:70489): WARNING **: 19:46:07.080: Failed to load shared library
On Mar 17, 2021, at 04:07, joerg van den hoff wrote:
> On 17.03.21 05:07, Ryan Schmidt wrote:
>> On Mar 16, 2021, at 13:47, joerg van den hoff wrote:
>>> "** (meld:70489): WARNING **: 19:46:07.080: Failed to load shared library
>>> './gtksourceview/libgtksourceview-4.0.dylib' referenced by the
On 17.03.21 05:07, Ryan Schmidt wrote:
On Mar 16, 2021, at 13:47, joerg van den hoff wrote:
"** (meld:70489): WARNING **: 19:46:07.080: Failed to load shared library
'./gtksourceview/libgtksourceview-4.0.dylib' referenced by the typelib:
dlopen(./gtksourceview/libgtksourceview-4.0.dylib,
13 matches
Mail list logo
