Peter T. Breuer:
> oboe:/usr/oboe/ptb% elm
> I can't understand keyword "local-fast-lookup" in line 18 in ".elm/elmrc"
> file
> Fix .elm/elmrc or let elm rebuild elmrc with option '-w'
>
> followed by bailout.
>
> So the workaround is untenable on a system with NFS shared home
> directorie
Peter T. Breuer:
> > That option have following description:
> >
> > # If set indicates that directory listing not needed for lookup
>
> ?? Double dutch! Lookup of what? What directory listing?
>
> > # Need to be unset, if same character on local-fs-charset is several
> > # repesentations (or en
"A month of sundays ago Kari Hurtta wrote:"
> Peter T. Breuer:
> > oboe:/usr/oboe/ptb% elm
> > I can't understand keyword "local-fast-lookup" in line 18 in ".elm/elmrc"
> > file
> > Fix .elm/elmrc or let elm rebuild elmrc with option '-w'
> >
> > followed by bailout.
> >
> > So the workaro
Peter T. Breuer:
> IMO it's simply a programming error, and the simplest thing is to
> correct it. Are you saying that this behaviour is _intentional_? What is
> its objective?
Doing directory lookup is _intentional_.
Statting perhaps can be delayed until someone asks flags
for entry from Elm's i
"A month of sundays ago Kari Hurtta wrote:"
> Peter T. Breuer:
> > IMO it's simply a programming error, and the simplest thing is to
> > correct it. Are you saying that this behaviour is _intentional_? What is
> > its objective?
>
> Doing directory lookup is _intentional_.
Then what is its intent
Peter T. Breuer:
> Yes, statting is precisely the problem. Or more accurately, statting
> all the entries BENEATH all the directories that form initial segments
> of the path to the system mailbox is the problem.
You claim that.
elm -f
does
new_browser(..) [see src/init.c]
but w
Peter T. Breuer:
> > Statting perhaps can be delayed until someone asks flags
> > for entry from Elm's internal directory browser.
>
> Flags for entry? Asks FOR flags? I'm afraid I don't follow .. what is
> this about flags? And what is an internal directory browser .. elm
> doesn't browse, d
"A month of sundays ago Kari E. Hurtta wrote:"
> Peter T. Breuer:
> > Yes, statting is precisely the problem. Or more accurately, statting
> > all the entries BENEATH all the directories that form initial segments
> > of the path to the system mailbox is the problem.
>
> You claim that.
>
> elm
"A month of sundays ago Kari E. Hurtta wrote:"
> Peter T. Breuer:
> > Flags for entry? Asks FOR flags? I'm afraid I don't follow .. what is
> > this about flags? And what is an internal directory browser .. elm
> > doesn't browse, does it? It shows you all mailboxes if you type an
> > asteris
"A month of sundays ago Kari E. Hurtta wrote:"
> That is on chapter "Folder and file browser" on file README.ME+
Ecch .. I've just looked at that file. If it has chapters, that's
news. It looks like a mess and nothing more.
OK! I've now compiled elm with JUST DOTLOCKING, yay, and it no longer
ha
Package: clisp
Version: 1:2.27-0.5
Severity: wishlist
I wrote in clisp program that defines class with accessor to one of its
slots called type. I tried to run this program under Harlequin Lisp and
Alegro. Both reported an error, Harlequin said that type conflicts with
function visible from COMMO
11 matches
Mail list logo
