From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: Async pre-treatment of articles
Date: Sat, 28 Aug 2010 22:55:55 +0200 [thread overview]
Message-ID: <878w3q319g.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <m3occmsbzo.fsf@quimbies.gnus.org>
On Sat, 28 Aug 2010 22:44:59 +0200, Lars wrote:
> asjo@koldfront.dk (Adam Sjøgren) writes:
>> Looking at the http port with ngrep seems to confirm this. The article
>> is displayed, and a number of seconds (3-10) later, requests start going
>> out for the images.
> Oh, right. Yeah, w3m does seem ridiculously slow in fetching pictures.
> Perhaps I should peek at the w3m code instead.
It is just sitting there, doing nothing for ~10s. Then it looks like it
then runs w3m-idle-images-show() - I used toggle-debug-on-quit and
C-g'ed once in a while (XEmacs doing nothing), and then when I saw
requests going out in the ngrep-window, I C-g'ed and got this:
Debugger entered--Lisp error: (quit)
("next_event_internal()" "[internal]")
sit-for(0.1 t)
w3m-idle-images-show()
apply(w3m-idle-images-show nil)
byte-code("..." [this-command inhibit-quit quit-flag match-data itimer current-itimer match-data ((store-match-data match-data)) nil itimer-uses-arguments apply itimer-function itimer-function-arguments last-event-time next-wakeup itimers time-elapsed] 5)
itimer-run-expired-timers(13.331835)
itimer-timer-driver(nil)
("execute_internal_event()" "[internal]")
(dispatch-event "[internal]")
> Meanwhile, has anybody written a handy "how to use git from within Emacs
> if you're used to cvs-update and vc-mode... FOR DUMMIES"?
I think Magit is usually recommended, but it doesn't work in XEmacs, so
I haven't used it, and can't give any directions...
> I managed to check out the Gnus repository with password and stuff, but
> I'm not able to find out what magical keys to push to check stuff in
> again. (Yeah, I know, it's probably "push" in git parlance. But I'm
> covering my ears. LA LA LA LA LA. I can't hear you. LA LA LA.)
The really short command-line version:
git status ; lists the changes (shows hints on how to change status of things as well)
git add [file] ; add to list of things to commit
git commit -v ; commits the files you have added for commiting, locally
git push origin master ; push the commits you have made locally, out to the repository
Also:
git log ; to see the local commit log
git show [sha1] ; to see what a commit consists of
Best regards,
Adam
--
"Angels can fly because they take themselves lightly." Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2010-08-28 20:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 20:27 Lars Magne Ingebrigtsen
2010-08-28 20:34 ` Adam Sjøgren
2010-08-28 20:39 ` Adam Sjøgren
2010-08-28 20:44 ` Lars Magne Ingebrigtsen
2010-08-28 20:55 ` Adam Sjøgren [this message]
2010-08-28 20:59 ` Adam Sjøgren
2010-08-28 21:18 ` Lars Magne Ingebrigtsen
2010-08-28 21:21 ` Adam Sjøgren
2010-08-28 21:28 ` Lars Magne Ingebrigtsen
2010-08-28 21:44 ` Adam Sjøgren
2010-08-28 21:40 ` Lars Magne Ingebrigtsen
2010-08-28 23:54 ` Steinar Bang
2010-08-29 0:07 ` Lars Magne Ingebrigtsen
2010-08-29 13:36 ` Adam Sjøgren
2010-08-28 23:50 ` Steinar Bang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878w3q319g.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).