I had an accident with keystrokes (think: cat walked on keyboard) while I
was reading news with trn (version 4). Somehow, a certain thread got
marked as "memorized", so that whenever I join that particular group, it
gets "selected". I, of course, want to undo this operation.
tl;dr: I eventually figured out that hitting T then c on that thread would >"de-memorize" it, so problem is solved. However, ...
I would like to know how/where this command gets stored - so that I could >just edit it out of that file.
I had an accident with keystrokes (think: cat walked on keyboard) while I >>was reading news with trn (version 4). Somehow, a certain thread got >>marked as "memorized", so that whenever I join that particular group, it >>gets "selected". I, of course, want to undo this operation.
tl;dr: I eventually figured out that hitting T then c on that thread would >>"de-memorize" it, so problem is solved. However, ...
I would like to know how/where this command gets stored - so that I could >>just edit it out of that file.
In a specific newsgroup, ^k will bring up the kill file for editing.
Mine are in ~/News/Kill. I don't remember if that's default or I set
that somewhere.
Adam H. Kerman <ahk@chinet.com> wrote:
Kenny McCormack <gazelle@shell.xmission.com> wrote:
I had an accident with keystrokes (think: cat walked on keyboard) while I >>>was reading news with trn (version 4). Somehow, a certain thread got >>>marked as "memorized", so that whenever I join that particular group, it >>>gets "selected". I, of course, want to undo this operation.
tl;dr: I eventually figured out that hitting T then c on that thread would >>>"de-memorize" it, so problem is solved. However, ...
I would like to know how/where this command gets stored - so that I could >>>just edit it out of that file.
In a specific newsgroup, ^k will bring up the kill file for editing.
Mine are in ~/News/Kill. I don't remember if that's default or I set
that somewhere.
Thanks, but I have already painstakingly established that they are not there.
They are somewhere else.
I had an accident with keystrokes (think: cat walked on keyboard) while I
was reading news with trn (version 4). Somehow, a certain thread got
marked as "memorized", so that whenever I join that particular group, it
gets "selected". I, of course, want to undo this operation.
tl;dr: I eventually figured out that hitting T then c on that thread would "de-memorize" it, so problem is solved. However, ...
I would like to know how/where this command gets stored - so that I could just edit it out of that file. I know about killfiles and where they are stored and frequently end up editing them by hand, so no problem doing that if needed. But, here's the thing:
1) Everything in the man page ("man trn"), says that "memorized"
commands are stored in the killfile (either the so-called "global"
killfile or the group-specific killfile). But this doesn't seem to
be the case, because...
2) There was nothing in either killfile that had to do with
the memorization of this thread. I can tell this by the access
date/time on the killfile file and/or by comparing the file (via
the "diff" utility) to a previous version of it. I can state with
pretty close to total certainty, that there's nothing in either
file having to do with this memorization stuff.
So, it must be stored somewhere else. Where?
P.S. I suspect that something got changed in the software and the docs
(the man page) was not updated. So, they are out of sync.
On 2021-05-23, Kenny McCormack <gazelle@shell.xmission.com> wrote:
I had an accident with keystrokes (think: cat walked on keyboard) while I
was reading news with trn (version 4). Somehow, a certain thread got
marked as "memorized", so that whenever I join that particular group, it
gets "selected". I, of course, want to undo this operation.
tl;dr: I eventually figured out that hitting T then c on that thread would >> "de-memorize" it, so problem is solved. However, ...
I would like to know how/where this command gets stored - so that I could
just edit it out of that file. I know about killfiles and where they are
stored and frequently end up editing them by hand, so no problem doing that >> if needed. But, here's the thing:
1) Everything in the man page ("man trn"), says that "memorized"
commands are stored in the killfile (either the so-called "global"
killfile or the group-specific killfile). But this doesn't seem to
be the case, because...
2) There was nothing in either killfile that had to do with
the memorization of this thread. I can tell this by the access
date/time on the killfile file and/or by comparing the file (via
the "diff" utility) to a previous version of it. I can state with
pretty close to total certainty, that there's nothing in either
file having to do with this memorization stuff.
So, it must be stored somewhere else. Where?
P.S. I suspect that something got changed in the software and the docs
(the man page) was not updated. So, they are out of sync.
use the source, Luke
2) There was nothing in either killfile that had to do with
the memorization of this thread. I can tell this by the access
date/time on the killfile file and/or by comparing the file (via
the "diff" utility) to a previous version of it. I can state with
pretty close to total certainty, that there's nothing in either
file having to do with this memorization stuff.
Or you, know, just delete the whole savedscores file.
Eli the Bearded <*@eli.users.panix.com> wrote:
Or you, know, just delete the whole savedscores file.Or rename it with a "funny" name so trn can't find it.
In news.software.readers, Steven M. O'Neill <steveo@panix.com> wrote:
Eli the Bearded <*@eli.users.panix.com> wrote:
Or you, know, just delete the whole savedscores file.Or rename it with a "funny" name so trn can't find it.
Perhaps you could future proof that with:
ed ~/.trn/trnrc <<_EDIT
/^\[environment\]
a
SAVESCOREFILE=/dev/null
.
w
q
_EDIT
Elijah
------
/dev/null is funny, right?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 483 |
Nodes: | 16 (2 / 14) |
Uptime: | 148:43:36 |
Calls: | 9,591 |
Calls today: | 5 |
Files: | 13,676 |
Messages: | 6,148,235 |
Posted today: | 2 |