flee@shire.cs.psu.edu (Felix Lee) (01/07/90)
Last I remember, Masanobu UMEDA disappeared and hasn't been heard from since. Are you still out there? If not, is there anyone actively supporting GNUS? Or is anyone willing to take up the reins? Will there ever be a GNUS 3.13, or would that be bad luck? -- Felix Lee flee@shire.cs.psu.edu *!psuvax1!flee
tale@cs.rpi.edu (David C Lawrence) (01/08/90)
In article <Cyg.ki@cs.psu.edu> flee@shire.cs.psu.edu (Felix Lee) writes: > Last I remember, Masanobu UMEDA disappeared and hasn't been heard from > since. Are you still out there? If not, is there anyone actively > supporting GNUS? Or is anyone willing to take up the reins? Will > there ever be a GNUS 3.13, or would that be bad luck? I am semi-actively supporting it for a few people around the net who've asked me to get it to do this-or-that for them. I was planning on releasing a new gnus-user-tale.el in a couple of weeks that dealt with this wishlist of mine: a forward function for GNUS. ================ modifiy GNUS to check for #.newsrc#. ================ modify GNUS to look for a followups file or variable to auto-direct replies to the right place if none is there. (Original idea c/o amanda@intercon.com (Amanda Walker)) ================ Hack GNUS's signature mechanism to allow more variety, easily and automatically ================ Kludge around hardcoded C-h crud in people's messages. ================ Find out how come GNUS doesn't like =group in active file. ================ Retrieving articles from a newsgroup with GNUS, something in addition to gnus-large-newsgroup is needed. ranges/specific article num would be nice. ================ Change GNUS to make .newsrc a hidden buffer. ================ Fix up the sort call in gnus-save-newsrc-assoc to do a copy-sequence first. ================ Make gnus-signature-file buffer local ================ Make GNUS ignore null followup-to field. ================ Add a "finger author" feature to GNUS ================ GNUS catch-up-group-and-exit -- see if should select next group automatically. ================ Don't have GNUS put in Followup-To: automatically, ever. ================ Bag most of the Distribution: stuff; it is misleading because most people don't know how broken that header line is. ================ From kcollett@urbana.mcd.mot.com Tue Dec 12 16:35:59 1989 From: kcollett@urbana.mcd.mot.com (Kendall Collett) Subject: XHDR nntp command Date: 11 Dec 89 18:53:17 GMT Are there any plans to modify GNUS to use the XHDR NNTP command? (Or has anybody modified GNUS to do so?) ================ Figure out mysterious bug where point in *Subject* window sometimes ends up on a random other line when an article is selected. ================ Some of these have already been done, some haven't. I'm not sure yet when I'll feel comfortable with releasing it, but hopefully before the end of the month. Dave -- (setq mail '("tale@cs.rpi.edu" "tale@ai.mit.edu" "tale@rpitsmts.bitnet"))
rich@sendai.sendai.ann-arbor.mi.us (K. Richard Magill) (01/08/90)
In article <Cyg.ki@cs.psu.edu> flee@shire.cs.psu.edu (Felix Lee) writes:
Last I remember, Masanobu UMEDA disappeared and hasn't been heard
from since. Are you still out there?
As I recall, his last words were something to the effect of "I'm
switching jobs; they don't have net access yet, but I'm working on
it."pcg@aber-cs.UUCP (Piercarlo Grandi) (01/10/90)
In article <%&LY9@rpi.edu> tale@cs.rpi.edu (David C Lawrence) writes:
I am semi-actively supporting it for a few people around the net
who've asked me to get it to do this-or-that for them. I was planning
on releasing a new gnus-user-tale.el in a couple of weeks that dealt
with this wishlist of mine:
I have trwo long standing wishes, please grant me them:
1) to have the proper mode line for the Subject and Article
buffers... (currently Subject has the title of the most recently
visited article, and Article has the name of the newsgroup).
2) To have by default a few sorting options, and all sorting be
done by primary key to be chosen, and always have date sent as
secondary key. As primary keys I'd like subject, author, article
number, none; the default shopuld be either none (sorting on
date sent only) or article number or, preferably, subject. I'd
like this not be done with setting a hook, just a variable.
--
Piercarlo "Peter" Grandi | ARPA: pcg%cs.aber.ac.uk@nsfnet-relay.ac.uk
Dept of CS, UCW Aberystwyth | UUCP: ...!mcvax!ukc!aber-cs!pcg
Penglais, Aberystwyth SY23 3BZ, UK | INET: pcg@cs.aber.ac.uktrost@reed.bitnet (Bill Trost) (01/11/90)
In his wishlist, tale@cs.rpi.edu writes: >Retrieving articles from a newsgroup with GNUS, something in addition >to gnus-large-newsgroup is needed. ranges/specific article num would be nice. Something I would like to see that would nicely *replace* the large newsgroup stuff would be background acquisition of news articles. I imagine some loop somewhere (called after "n" and " " and "." and other common news-reading keys) like (while (not (input-pending-p)) (gnus-fetch-next-header)) I've started looking at the code, but it's much too complicated for me to do anything like this in the near future. David, how long do you think it would take you to pull off something like this?
tale@cs.rpi.edu (David C Lawrence) (01/12/90)
In article <13853@reed.UUCP> trost@reed.bitnet (Bill Trost) writes: > Something I would like to see that would nicely *replace* the large > newsgroup stuff would be background acquisition of news articles. I > imagine some loop somewhere (called after "n" and " " and "." and > other common news-reading keys) like > (while (not (input-pending-p)) > (gnus-fetch-next-header)) This seems like a good topic to discuss in this forum now. I don't know the best solution, but I don't think this rough idea is feasible. Then again, it could just be my own short-sightedness because of the way I read news compared to the way other people do. I recognise these differences though and am open for suggestions. These differences are part of what make me not like nn very much even though other people love it. A few months ago someone asked me if I/he/we (I don't remember) could make GNUS retrieve newsgroups in the background as an asynchronous procedure. While my initial reaction was, "Yeah! Should work on that ..." I soon realised that it was not such a hot idea because GNUS takes over again as soon as its headers are retrieved. That is, you could say, "Crap! 707 articles in comp.windows.x! I think I'll edit foo.c while it is retrieving them." So you go off and start editing foo.c and as soon as those articles are all retrieved GNUS kicks in again and takes over your environment, possibly grabbing keystrokes that you just intended to be part of a printf call. There seem to be a couple of different possibilities here. It could just check to see whether you are in the *Newsgroup* or *Subject* buffer when it has all of the information it wants. If not, then it would just politely put a message in the echo area, with a ding, telling you that your *Subject* buffer is ready. But then how should you get to it? People like me who have gnus-use-full-window non-nil and gnus-window-configuration set to mimic pre-3.12 behaviour would have no problem just doing a switch-to-buffer and continuing from there. But what about the people who want a special window configuration? Another thing to bear in mind is that while GNUS is retrieving its articles via NNTP it would a) be very easy to do asynchronously but b) make working extremely slow as all of that data was being shoved through the filter every second anyway. When using local spool (including NFS/RFS/FooFS) then you could make it so the speed was less of a problem but making it asynchronous would be a little harder. In the example above, say input is pending. So you exit your loop and have it execute the command it was just given. How would that be done very cleanly, especially so that the loop was re-entered after the command was executed? You could read keys and process them as applicable but at the moment there seems to be no nice way of modifying the context that the command might want to modify yet keeping everything else as it was. I say "at the moment" because there might indeed be an elegant way to accomplish this that is just not firing on my tired synapses right now. Suggestions are welcome, preferably public on this list/group as I would appreciate open discussion on what people think is The Right Thing. It seems that such discussion often has the potential to flush out ideas that wouldn't otherwise be heard. It also might incite someone like Roland (who has also hacked GNUS) to do it sooner than I will likely be able to get to it. > David, how long do you think it would take you to pull off something > like this? Given my current work load and a somewhat unclear direction to proceed in, probably not before the end of the month. I don't know beyond that. Dave -- (setq mail '("tale@cs.rpi.edu" "tale@ai.mit.edu" "tale@rpitsmts.bitnet"))