From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 5BD17789EC for ; Thu, 24 Sep 2015 10:39:52 -0700 (PDT) Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-08v.sys.comcast.net with comcast id M5i01r00327uzMh015j1RY; Thu, 24 Sep 2015 17:43:01 +0000 Received: from eklhad ([IPv6:2601:405:4002:b0a:21e:4fff:fec2:a0f1]) by resomta-ch2-02v.sys.comcast.net with comcast id M5j11r0070GArqr015j1s3; Thu, 24 Sep 2015 17:43:01 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.4.2+ Date: Thu, 24 Sep 2015 13:43:01 -0400 Message-ID: <20150824134301.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1443116581; bh=JmQzGRVXVUiVyJ5Agh/M7Me9igJUDAPFjyrNtqEIKZ0=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=CEijYse3saoWLf1SIWFKqTkdP/q1F8s2Ln6ugtgjrhTlL/zQ0eAnF1iHXUkKwznaX +tbamwr6KCHEbjuJbj1tY8VtcYZsdJaio/rh56wP8qV0OJpx3Ugeo81Kw0c0qhIMhS QGJtiAyxJ7zQhNKTMRdQ7cbpw4HjRGVXU4ali5GUlXbOgIE5xWdMQJKfnoZ1Rzuw9a +gidGPK643UofDwbgoC/tSYpq8Kp3/p8oK+sAnYAjCK1A5FFYQco1oXPjon+yRHJB6 GqoO2tKX6MoEOZ7Jyefbzh06XSbUIDwASw+M9/R27WM8FTLHfOAjgNfCjZho9DQA8l ycoZZFhBV3nOg== Subject: [Edbrowse-dev] file attributes on directory scan. X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 17:39:52 -0000 Ok, lsl lists the length of the file on the current line in directory mode, but ls=l fetches the length of every file in subsequent directory scans. See the documentation for more details. Browsed usersguide line 1072. As mentioned earlier, I had to muck with the code in many places. reading or writing a file, a directory, what was a directory into a file, or into another session, or reading another session into this one, maybe it was a directory listing maybe not, and so on. After a day or so of work I thought I had it all working, I made one tiny change to buffers.c, and wrote the file, and file write failed. I had broken something, badly! buffers.c was now 13 bytes long, and all my work was lost. It's amazing how we rely on this program, and how frightening when it doesn't work. So I had lost all that effort, or had I? All the new software was still in the buffer, I just couldn't write it anywhere. But I could print it, and I have a linear adapter. My linear "screen" is smaller than buffers.c, so I printed the first 2000 lines, then saved the screen to a temp file, then the next 2000, and so on, and then I put the files together and reproduced buffers.c. Holy crap! Course printing turned tabs into spaces, so I had to run it through indent again. My file was back! Always best if you don't panic. Finally I used ed to find and fix the writing bug, wrote bufffers.c, recompiled, tested, and it seems to work again. But wow! Always keep backups of your work or important files, even just a few hours work, copy the file to /tmp or something just to be safe. Anyways, try setting ls=st or some such and edit a directory. Honestly I probably won't use this full scan feature very often, too much clutter for me, but sometimes I just want to know the size or time of one of the files in my listing, and I can use lss or lst for that, and that meets my needs. Karl Dahlke