Re: [dev] wmii falling out of favor
On Mon, Jan 2, 2012 at 7:02 AM, Patrick Haller
<201009-suckl...@haller.ws> wrote:
> On 2012-01-01 21:13, Suraj N. Kurapati wrote:
>> So I considered the trade-offs between SLOC minimalism, project and
>> community activity, and my productivity in DWM vs. WMII and finally
>> decided to switch back to WMII (which I used since six years prior).
>
> How often do people re-evaluate their toolsets?
>
> With my shell, I can examine shell history and do stuff like:
> cd() {
> dir="$1"
> test -f $1 && dir=`dirname $1`
> builtin cd "$dir" && ls | sed 10q | fmt -w $COLUMNS
> }
>
> With X11, do we screencast a day's work and watch it in fast-forward?
That's related to one of the reasons I tend to prefer doing stuff on
the command line: we know how to record textual operations and search
them relatively efficiently. On my machine each terminal's history
file is given a unique name and the each command (command, not output)
is stored as a (time, current directory, command) in the file and the
files are stored "forever" (minus a couple of simple space savers like
not storing incredibly frequent commands like pwd, df, ls, etc). Then
months later I can often figure out something that I did from a vague
memory (eg, "I'm sure I had to hack a symlink to a library to make
something work a couple of months ago, which ln -s commands did I
issue around the time my cwd was last trialProgSource?") I don't do it
often, but occasionally it comes up and saves me an hour or two
investigation.
I'm not aware of any way of either storing or, more importantly,
searching a user's interaction with the GUI apps on a computer system.
--
cheers, dave tweed__
computer vision researcher: david.tw...@gmail.com
"while having code so boring anyone can maintain it, use Python." --
attempted insult seen on slashdot
[dev] Logging Commands
On Thu, 05 Jan 2012 14:19:00 -, David Tweed wrote: I'm not aware of any way of either storing or, more importantly, searching a user's interaction with the GUI apps on a computer system. Some GUI programs such as Netsurf log user actions for later inspection.[1] GNOME Zeitgeist is also interesting in this respect, although their pride of running "in under 10mb RAM" is a fair complaint on this list. Unless they've actually invented centibit random-access memory, in which case I would grudgingly consider it acceptable. For those of you that stick to lynx no matter what, Netsurf represents visited pages as thumbnails in a tree, as opposed to lines of text. 1: http://www.netsurf-browser.org/documentation/guide#History
Re: [dev] wmii falling out of favor
Hey, On 5 January 2012 14:19, David Tweed wrote: > I'm not aware of any way of either storing or, more importantly, > searching a user's interaction with the GUI apps on a computer system. That's not inherent to GUIs, it just so happens that existing GUIs are extremely poorly made. It's not interaction which needs to be logged so much as the modification of persistent data -- files and such -- which could easily be logged by graphical apps. The more I think about it the more I believe terminals only continue to be used because of how awfully bad the alternatives are. cls
Re: [dev] wmii falling out of favor
On Thu, Jan 05, 2012 at 11:12:44PM +, Connor Lane Smith wrote: > That's not inherent to GUIs, it just so happens that existing GUIs are > extremely poorly made. It's not interaction which needs to be logged > so much as the modification of persistent data -- files and such -- > which could easily be logged by graphical apps. This just changes the question from "what did you do?" to "what the hell caused that change?" Both of these things need to be logged.
