* State of the art for HTML email
@ 2011-02-24 0:11 Norman Walsh
2011-02-24 0:18 ` Edward O'Connor
2011-02-24 7:58 ` Steinar Bang
0 siblings, 2 replies; 21+ messages in thread
From: Norman Walsh @ 2011-02-24 0:11 UTC (permalink / raw)
To: ding
[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]
Hello world,
I apologize for a message that is perhaps only tangentially related
(but as a long time Gnus user, I will assert that it is at least
tangentially related :-) ).
I seem to have accumulated a no longer insignificant minority of
colleagues who insist on sending me HTML email. Mostly I file it in
the bit bucket and figure "fsck 'em", but periodically I actually do
care about the message.
Sometimes "W h" gets the job done. But sometimes the messages include
inline images. In those cases, "W h" often makes things worse. What I
see is something like this:
1. (*) text/plain ( ) text/html
From: John Doe (john.doe@example.org)
To: Some Address (someone@example.com)
What: Issue Created
Link: https://example.com/browse/UOV-235
----
Dear John
I have observed a severe bug...
1. I choose the Frobnitz Widget. Fine so far.
[cid:22DAA184-A92E-4788-9E00-8A0F4184DB75@xxx.example.org]
...
What's the state of the art for dealing with messages like this in
Gnus? Emacs 23 can display inline graphics, so I'd probably be content
if I could just make [cid:xxx] elements resolve to the images.
I'll be honest, I usually just bail at this point and run 'ripmime' in
/tmp and look at the images out-of-band. But that's a PITA.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Labor, n. One of the processes by which
http://nwalsh.com/ | A acquires property for B.--Ambrose
| Bierce
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: State of the art for HTML email
2011-02-24 0:11 State of the art for HTML email Norman Walsh
@ 2011-02-24 0:18 ` Edward O'Connor
2011-02-24 0:23 ` Norman Walsh
2011-02-24 7:49 ` Reiner Steib
2011-02-24 7:58 ` Steinar Bang
1 sibling, 2 replies; 21+ messages in thread
From: Edward O'Connor @ 2011-02-24 0:18 UTC (permalink / raw)
To: Norman Walsh; +Cc: ding
Hi,
> I seem to have accumulated a no longer insignificant minority of
> colleagues who insist on sending me HTML email.
Isn't it horrible? Nevertheless...
> Sometimes "W h" gets the job done. But sometimes the messages include
> inline images. In those cases, "W h" often makes things worse
[snip]
> What's the state of the art for dealing with messages like this in
> Gnus?
Personally, I use emacs-w3m to render HTML email, which usually
handles things just fine. When it's not enough, K H does the trick (I
think this was introduced in a recentish No Gnus).
If you'd like help setting up emacs-w3m under a sufficiently Unixoid
OS, let me know off-list and I can walk you through it on IRC.
Ted
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: State of the art for HTML email
2011-02-24 0:18 ` Edward O'Connor
@ 2011-02-24 0:23 ` Norman Walsh
2011-02-24 23:08 ` Dave Goldberg
2011-02-24 7:49 ` Reiner Steib
1 sibling, 1 reply; 21+ messages in thread
From: Norman Walsh @ 2011-02-24 0:23 UTC (permalink / raw)
To: ding
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
"Edward O'Connor" <hober0@gmail.com> writes:
> Personally, I use emacs-w3m to render HTML email, which usually
> handles things just fine. When it's not enough, K H does the trick (I
> think this was introduced in a recentish No Gnus).
Oh, I say! "K H" is fairly cool. Unfortunately, it doesn't seem to
handle inlined images. Does emacs-w3m actually do images, I thought
that was one of the text-only alternatives? But maybe I'm out of
touch.
>
> If you'd like help setting up emacs-w3m under a sufficiently Unixoid
> OS, let me know off-list and I can walk you through it on IRC.
Thanks. I'll poke about a bit and see what I can manage.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Don't part with your illusions. when
http://nwalsh.com/ | they are gone you may still exist, but
| you have ceased to live.--Mark Twain
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: State of the art for HTML email
2011-02-24 0:23 ` Norman Walsh
@ 2011-02-24 23:08 ` Dave Goldberg
2011-02-25 15:46 ` Norman Walsh
0 siblings, 1 reply; 21+ messages in thread
From: Dave Goldberg @ 2011-02-24 23:08 UTC (permalink / raw)
To: ding
> "Edward O'Connor" <hober0@gmail.com> writes:
>> Personally, I use emacs-w3m to render HTML email, which usually
>> handles things just fine. When it's not enough, K H does the trick (I
>> think this was introduced in a recentish No Gnus).
> Oh, I say! "K H" is fairly cool. Unfortunately, it doesn't seem to
> handle inlined images. Does emacs-w3m actually do images, I thought
> that was one of the text-only alternatives? But maybe I'm out of
> touch.
I don't have a good example handy as I'm not at work but in some update within the last year, I think by Katsumi Yamaoka, fixed K H to dtrt with inlined images. I know it's been working for me.
That said, the improvements to gnus-html, in conjunction with w3m, tend to render html email, inlined images included, well enough that I don't need K H quite as much as I used to.
--
Dave Goldberg
david.goldberg6@verizon.net
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: State of the art for HTML email
2011-02-24 23:08 ` Dave Goldberg
@ 2011-02-25 15:46 ` Norman Walsh
0 siblings, 0 replies; 21+ messages in thread
From: Norman Walsh @ 2011-02-25 15:46 UTC (permalink / raw)
To: ding
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
david.goldberg6@verizon.net (Dave Goldberg) writes:
> That said, the improvements to gnus-html, in conjunction with w3m,
> tend to render html email, inlined images included, well enough that I
> don't need K H quite as much as I used to.
Ok, that was definitely worth the half hour or so of fiddling that it
took. Using emacs-w3m is definitely an improvement. Thanks, all!
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Art is not a mirror held up to reality
http://nwalsh.com/ | but a hammer with which to shape
| it.--Bertold Brecht
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: State of the art for HTML email
2011-02-24 0:18 ` Edward O'Connor
2011-02-24 0:23 ` Norman Walsh
@ 2011-02-24 7:49 ` Reiner Steib
2011-02-24 11:42 ` Norman Walsh
1 sibling, 1 reply; 21+ messages in thread
From: Reiner Steib @ 2011-02-24 7:49 UTC (permalink / raw)
To: ding
On Thu, Feb 24 2011, Edward O'Connor wrote:
> Personally, I use emacs-w3m to render HTML email, which usually
> handles things just fine. When it's not enough, K H does the trick (I
> think this was introduced in a recentish No Gnus).
"Recent" like "introduced in 2006"? :-)
I'm not sure if I understood Norman's problem correctly, but
`gnus-mime-display-multipart-related-as-mixed' might be helpful.
,----[ <f1> v gnus-mime-display-multipart-related-as-mixed RET ]
| gnus-mime-display-multipart-related-as-mixed is a variable defined
| in `gnus-art.el'.
| Its value is t
|
|
| Documentation:
| Display "multipart/related" parts as "multipart/mixed".
|
| If displaying "text/html" is discouraged (see
| `mm-discouraged-alternatives') images or other material inside a
| "multipart/related" part might be overlooked when this variable is nil.
|
| You can customize this variable.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: State of the art for HTML email
2011-02-24 0:11 State of the art for HTML email Norman Walsh
2011-02-24 0:18 ` Edward O'Connor
@ 2011-02-24 7:58 ` Steinar Bang
2011-02-24 12:28 ` Lars Ingebrigtsen
2011-02-24 12:55 ` Recursive require with emacs24? Norman Walsh
1 sibling, 2 replies; 21+ messages in thread
From: Steinar Bang @ 2011-02-24 7:58 UTC (permalink / raw)
To: ding
I haven't tried it myself, but if you have emacs24, linked with libxml2,
I believe there is a native HTML renderer now. I don't know how well it
does pictures.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: State of the art for HTML email
2011-02-24 7:58 ` Steinar Bang
@ 2011-02-24 12:28 ` Lars Ingebrigtsen
2011-02-24 12:55 ` Recursive require with emacs24? Norman Walsh
1 sibling, 0 replies; 21+ messages in thread
From: Lars Ingebrigtsen @ 2011-02-24 12:28 UTC (permalink / raw)
To: ding
Steinar Bang <sb@dod.no> writes:
> I haven't tried it myself, but if you have emacs24, linked with libxml2,
> I believe there is a native HTML renderer now. I don't know how well it
> does pictures.
It does pictures quite well. :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 21+ messages in thread
* Recursive require with emacs24?
2011-02-24 7:58 ` Steinar Bang
2011-02-24 12:28 ` Lars Ingebrigtsen
@ 2011-02-24 12:55 ` Norman Walsh
2011-02-24 13:11 ` Steinar Bang
2011-02-25 3:39 ` Lars Ingebrigtsen
1 sibling, 2 replies; 21+ messages in thread
From: Norman Walsh @ 2011-02-24 12:55 UTC (permalink / raw)
To: ding
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
Steinar Bang <sb@dod.no> writes:
> I haven't tried it myself, but if you have emacs24, linked with libxml2,
> I believe there is a native HTML renderer now. I don't know how well it
> does pictures.
So, I went off and built emacs24 to see what that was like...but I get
a strange error about "recursive require for 'gnus-sum in ~/.gnus"
when I try to load either the gnus that's part of emacs24 or the
nognus-0.13 that I downloaded yesterday.
This happens even if I remove all the require's from my .gnus file.
$ grep require .gnus | grep -v ^\;
$
Uhm. Just me?
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Any sufficiently undocumented code is
http://nwalsh.com/ | indistinguishable from magic.
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: Recursive require with emacs24?
2011-02-24 12:55 ` Recursive require with emacs24? Norman Walsh
@ 2011-02-24 13:11 ` Steinar Bang
2011-02-25 3:39 ` Lars Ingebrigtsen
1 sibling, 0 replies; 21+ messages in thread
From: Steinar Bang @ 2011-02-24 13:11 UTC (permalink / raw)
To: ding
>>>>> Norman Walsh <ndw@nwalsh.com>:
> So, I went off and built emacs24 to see what that was like...but I get
> a strange error about "recursive require for 'gnus-sum in ~/.gnus"
> when I try to load either the gnus that's part of emacs24 or the
> nognus-0.13 that I downloaded yesterday.
> This happens even if I remove all the require's from my .gnus file.
> $ grep require .gnus | grep -v ^\;
> $
> Uhm. Just me?
Hm... I haven't tried emacs 24 yet, but I have the following at the
start of my .gnus.el:
; git gnus specific variables at the start. Remove when going production.
(load "gnus-load")
The stuff in gnus-load is related to using no gnus, I think.
But that shouldn't be needed when using the native emacs24 gnus, I
guess...?
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Recursive require with emacs24?
2011-02-24 12:55 ` Recursive require with emacs24? Norman Walsh
2011-02-24 13:11 ` Steinar Bang
@ 2011-02-25 3:39 ` Lars Ingebrigtsen
2011-02-25 15:19 ` Norman Walsh
1 sibling, 1 reply; 21+ messages in thread
From: Lars Ingebrigtsen @ 2011-02-25 3:39 UTC (permalink / raw)
To: ding
Norman Walsh <ndw@nwalsh.com> writes:
> This happens even if I remove all the require's from my .gnus file.
>
> $ grep require .gnus | grep -v ^\;
> $
Do you have any `load' statements?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Recursive require with emacs24?
2011-02-25 3:39 ` Lars Ingebrigtsen
@ 2011-02-25 15:19 ` Norman Walsh
2011-03-05 12:07 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 21+ messages in thread
From: Norman Walsh @ 2011-02-25 15:19 UTC (permalink / raw)
To: ding
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Do you have any `load' statements?
$ grep load .gnus | grep -v ^\;
(eval-after-load "gnus-sum"
(autoload 'bbdb-search "bbdb-com" "Insidious Big Brother Database autoload" t)
(autoload 'rmime-format "rmime" "" nil)
The eval-after-load expression is:
;; Highlight '#' marked summary lines
(eval-after-load "gnus-sum"
'(add-to-list
'gnus-summary-highlight
'((memq article gnus-newsgroup-processable)
. gnus-summary-high-read)))
I'm pretty sure I commented it out and it didn't fix the problem.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Some people can stay longer in an hour
http://nwalsh.com/ | than others can in a week
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: Recursive require with emacs24?
2011-02-25 15:19 ` Norman Walsh
@ 2011-03-05 12:07 ` Lars Magne Ingebrigtsen
2011-03-05 17:02 ` Andreas Schwab
2011-03-18 14:02 ` Recursive require with nognus? Norman Walsh
0 siblings, 2 replies; 21+ messages in thread
From: Lars Magne Ingebrigtsen @ 2011-03-05 12:07 UTC (permalink / raw)
To: ding
Norman Walsh <ndw@nwalsh.com> writes:
> I'm pretty sure I commented it out and it didn't fix the problem.
Try putting
(setq debug-on-error t)
as the first thing in .emacs. That will hopefully give you a backtrace
that'll tell you what's recursing.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Recursive require with emacs24?
2011-03-05 12:07 ` Lars Magne Ingebrigtsen
@ 2011-03-05 17:02 ` Andreas Schwab
2011-03-18 14:02 ` Recursive require with nognus? Norman Walsh
1 sibling, 0 replies; 21+ messages in thread
From: Andreas Schwab @ 2011-03-05 17:02 UTC (permalink / raw)
To: ding
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Norman Walsh <ndw@nwalsh.com> writes:
>
>> I'm pretty sure I commented it out and it didn't fix the problem.
>
> Try putting
>
> (setq debug-on-error t)
>
> as the first thing in .emacs. That will hopefully give you a backtrace
> that'll tell you what's recursing.
$ emacs --debug-init
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Recursive require with nognus?
2011-03-05 12:07 ` Lars Magne Ingebrigtsen
2011-03-05 17:02 ` Andreas Schwab
@ 2011-03-18 14:02 ` Norman Walsh
2011-03-18 18:42 ` nnir is pwetty kewl! (Was: Recursive require with nognus?) Steinar Bang
1 sibling, 1 reply; 21+ messages in thread
From: Norman Walsh @ 2011-03-18 14:02 UTC (permalink / raw)
To: ding
[-- Attachment #1: Type: text/plain, Size: 11178 bytes --]
When I initially reported this problem, I thought it was emacs24
related. It's not. <blush>I had the load-path wrong in my ~/.emacs so I
wasn't getting nognus, I was getting gnus 5.13 from the Emacs
distro.</blush>
Even with Emacs 23.2.1, if I put nognus-0.13 in my load path, I get
Error in ~/.gnus: Recurisve `require' for feature `gnus-sum'
during initialization.
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Try putting
>
> (setq debug-on-error t)
>
> as the first thing in .emacs. That will hopefully give you a backtrace
> that'll tell you what's recursing.
Yep. See below. It appears to my untrained eye, that the problem is in
gnus-sum and nnir: gnus-sum.el autoloads nnir and nnir requires
gnus-sum.
I don't think I'm trying to use nnir (it's not mentioned in my .gnus)
so I'm not sure why this is only happening to me...
Debugger entered--Lisp error: (error "Recursive `require' for feature `gnus-sum'")
require(gnus-sum)
byte-code("..!...!...!...!...!.....\"..F.B...D B...!....\"." [nnoo-definition-alist nnoo-state-alist require cl nnoo gnus-group gnus-sum gnus-util nnir mapcar #[(p) ".C." [p] 1] nil "*internal-non-initialized-backend*" nnoo-define-basics-1 gnus-declare-backend "nnir" mail] 4)
#<subr macroexpand>((nnir-article-rsv (mail-header-number gnus-tmp-header)) nil)
macroexpand((nnir-article-rsv (mail-header-number gnus-tmp-header)) nil)
macroexpand-all-1((nnir-article-rsv (mail-header-number gnus-tmp-header)))
gnus-macroexpand-all((nnir-article-rsv (mail-header-number gnus-tmp-header)))
byte-code("...!.BB...!.BB........!.BB...!.BB.....!.BB...!.BB.......!.BB.BB....!.BB.BB....!.BB.BB......................!D.@.BB.&." [78 macroexpand (mail-header-number gnus-tmp-header) (100) 83 (mail-header-subject gnus-tmp-header) (115) (115 gnus-tmp-subject-or-nil 115) (110 gnus-tmp-name 115) (65 (car ...) 115) (97 (or ... gnus-tmp-from) 115) (70 gnus-tmp-from 115) 120 (mail-header-xref gnus-tmp-header) (115) 68 (mail-header-date gnus-tmp-header) (115) (100 (gnus-dd-mmm ...) 115) (111 (gnus-date-iso8601 ...) 115) 77 (mail-header-id gnus-tmp-header) (115) 114 (mail-header-references gnus-tmp-header) (115) (99 (or ... 0) 100) (107 (gnus-summary-line-message-size gnus-tmp-header) 115) (76 gnus-tmp-lines 115) 90 or gnus-macroexpand-all (nnir-article-rsv (mail-header-number gnus-tmp-header)) (0) (100) 71 (nnir-article-group (mail-header-number gnus-tmp-header)) ("") (115) 103 (gnus-group-short-name (nnir-article-group ...)) ("") (115) (79 gnus-tmp-downloaded 99) (73 gnus-tmp-indentation 115) (84 (if ... "" ...) 115) (82 gnus-tmp-replied 99) (91 gnus-tmp-opening-bracket 99) (93 gnus-tmp-closing-bracket 99) (62 (make-string gnus-tmp-level 32) 115) ...] 41)
(defvar gnus-summary-line-format-alist (byte-code "...!.BB...!.BB........!.BB...!.BB.....!.BB...!.BB.......!.BB.BB....!.BB.BB....!.BB.BB......................!D.@.BB.&." [78 macroexpand ... ... 83 ... ... ... ... ... ... ... 120 ... ... 68 ... ... ... ... 77 ... ... 114 ... ... ... ... ... 90 or gnus-macroexpand-all ... ... ... 71 ... ... ... 103 ... ... ... ... ... ... ... ... ... ... ...] 41) "An alist of format specifications that can appear in summary lines.\nThese are paired with what variables they correspond with, along with\nthe type of the variable (string, integer, character, etc).")
require(gnus-sum)
byte-code("..!...!...!...!...!.....\"..F.B...D B...!....\"." [nnoo-definition-alist nnoo-state-alist require cl nnoo gnus-group gnus-sum gnus-util nnir mapcar #[(p) ".C." [p] 1] nil "*internal-non-initialized-backend*" nnoo-define-basics-1 gnus-declare-backend "nnir" mail] 4)
#<subr macroexpand>((nnir-article-rsv (mail-header-number gnus-tmp-header)) nil)
macroexpand((nnir-article-rsv (mail-header-number gnus-tmp-header)) nil)
macroexpand-all-1((nnir-article-rsv (mail-header-number gnus-tmp-header)))
gnus-macroexpand-all((nnir-article-rsv (mail-header-number gnus-tmp-header)))
byte-code("...!.BB...!.BB........!.BB...!.BB.....!.BB...!.BB.......!.BB.BB....!.BB.BB....!.BB.BB......................!D.@.BB.&." [78 macroexpand (mail-header-number gnus-tmp-header) (100) 83 (mail-header-subject gnus-tmp-header) (115) (115 gnus-tmp-subject-or-nil 115) (110 gnus-tmp-name 115) (65 (car ...) 115) (97 (or ... gnus-tmp-from) 115) (70 gnus-tmp-from 115) 120 (mail-header-xref gnus-tmp-header) (115) 68 (mail-header-date gnus-tmp-header) (115) (100 (gnus-dd-mmm ...) 115) (111 (gnus-date-iso8601 ...) 115) 77 (mail-header-id gnus-tmp-header) (115) 114 (mail-header-references gnus-tmp-header) (115) (99 (or ... 0) 100) (107 (gnus-summary-line-message-size gnus-tmp-header) 115) (76 gnus-tmp-lines 115) 90 or gnus-macroexpand-all (nnir-article-rsv (mail-header-number gnus-tmp-header)) (0) (100) 71 (nnir-article-group (mail-header-number gnus-tmp-header)) ("") (115) 103 (gnus-group-short-name (nnir-article-group ...)) ("") (115) (79 gnus-tmp-downloaded 99) (73 gnus-tmp-indentation 115) (84 (if ... "" ...) 115) (82 gnus-tmp-replied 99) (91 gnus-tmp-opening-bracket 99) (93 gnus-tmp-closing-bracket 99) (62 (make-string gnus-tmp-level 32) 115) ...] 41)
(defvar gnus-summary-line-format-alist (byte-code "...!.BB...!.BB........!.BB...!.BB.....!.BB...!.BB.......!.BB.BB....!.BB.BB....!.BB.BB......................!D.@.BB.&." [78 macroexpand ... ... 83 ... ... ... ... ... ... ... 120 ... ... 68 ... ... ... ... 77 ... ... 114 ... ... ... ... ... 90 or gnus-macroexpand-all ... ... ... 71 ... ... ... 103 ... ... ... ... ... ... ... ... ... ... ...] 41) "An alist of format specifications that can appear in summary lines.\nThese are paired with what variables they correspond with, along with\nthe type of the variable (string, integer, character, etc).")
require(gnus-sum)
byte-code("..!...!...!...!...!.....\"..F.B...D B...!....\"." [nnoo-definition-alist nnoo-state-alist require cl nnoo gnus-group gnus-sum gnus-util nnir mapcar #[(p) ".C." [p] 1] nil "*internal-non-initialized-backend*" nnoo-define-basics-1 gnus-declare-backend "nnir" mail] 4)
#<subr macroexpand>((nnir-article-rsv (mail-header-number gnus-tmp-header)) nil)
macroexpand((nnir-article-rsv (mail-header-number gnus-tmp-header)) nil)
macroexpand-all-1((nnir-article-rsv (mail-header-number gnus-tmp-header)))
gnus-macroexpand-all((nnir-article-rsv (mail-header-number gnus-tmp-header)))
byte-code("...!.BB...!.BB........!.BB...!.BB.....!.BB...!.BB.......!.BB.BB....!.BB.BB....!.BB.BB......................!D.@.BB.&." [78 macroexpand (mail-header-number gnus-tmp-header) (100) 83 (mail-header-subject gnus-tmp-header) (115) (115 gnus-tmp-subject-or-nil 115) (110 gnus-tmp-name 115) (65 (car ...) 115) (97 (or ... gnus-tmp-from) 115) (70 gnus-tmp-from 115) 120 (mail-header-xref gnus-tmp-header) (115) 68 (mail-header-date gnus-tmp-header) (115) (100 (gnus-dd-mmm ...) 115) (111 (gnus-date-iso8601 ...) 115) 77 (mail-header-id gnus-tmp-header) (115) 114 (mail-header-references gnus-tmp-header) (115) (99 (or ... 0) 100) (107 (gnus-summary-line-message-size gnus-tmp-header) 115) (76 gnus-tmp-lines 115) 90 or gnus-macroexpand-all (nnir-article-rsv (mail-header-number gnus-tmp-header)) (0) (100) 71 (nnir-article-group (mail-header-number gnus-tmp-header)) ("") (115) 103 (gnus-group-short-name (nnir-article-group ...)) ("") (115) (79 gnus-tmp-downloaded 99) (73 gnus-tmp-indentation 115) (84 (if ... "" ...) 115) (82 gnus-tmp-replied 99) (91 gnus-tmp-opening-bracket 99) (93 gnus-tmp-closing-bracket 99) (62 (make-string gnus-tmp-level 32) 115) ...] 41)
(defvar gnus-summary-line-format-alist (byte-code "...!.BB...!.BB........!.BB...!.BB.....!.BB...!.BB.......!.BB.BB....!.BB.BB....!.BB.BB......................!D.@.BB.&." [78 macroexpand ... ... 83 ... ... ... ... ... ... ... 120 ... ... 68 ... ... ... ... 77 ... ... 114 ... ... ... ... ... 90 or gnus-macroexpand-all ... ... ... 71 ... ... ... 103 ... ... ... ... ... ... ... ... ... ... ...] 41) "An alist of format specifications that can appear in summary lines.\nThese are paired with what variables they correspond with, along with\nthe type of the variable (string, integer, character, etc).")
require(gnus-sum)
byte-code("..!...!...!...!...!.....\"..F.B...D B...!....\"." [nnoo-definition-alist nnoo-state-alist require cl nnoo gnus-group gnus-sum gnus-util nnir mapcar #[(p) ".C." [p] 1] nil "*internal-non-initialized-backend*" nnoo-define-basics-1 gnus-declare-backend "nnir" mail] 4)
#<subr macroexpand>((nnir-article-rsv (mail-header-number gnus-tmp-header)) nil)
macroexpand((nnir-article-rsv (mail-header-number gnus-tmp-header)) nil)
macroexpand-all-1((nnir-article-rsv (mail-header-number gnus-tmp-header)))
gnus-macroexpand-all((nnir-article-rsv (mail-header-number gnus-tmp-header)))
byte-code("...!.BB...!.BB........!.BB...!.BB.....!.BB...!.BB.......!.BB.BB....!.BB.BB....!.BB.BB......................!D.@.BB.&." [78 macroexpand (mail-header-number gnus-tmp-header) (100) 83 (mail-header-subject gnus-tmp-header) (115) (115 gnus-tmp-subject-or-nil 115) (110 gnus-tmp-name 115) (65 (car ...) 115) (97 (or ... gnus-tmp-from) 115) (70 gnus-tmp-from 115) 120 (mail-header-xref gnus-tmp-header) (115) 68 (mail-header-date gnus-tmp-header) (115) (100 (gnus-dd-mmm ...) 115) (111 (gnus-date-iso8601 ...) 115) 77 (mail-header-id gnus-tmp-header) (115) 114 (mail-header-references gnus-tmp-header) (115) (99 (or ... 0) 100) (107 (gnus-summary-line-message-size gnus-tmp-header) 115) (76 gnus-tmp-lines 115) 90 or gnus-macroexpand-all (nnir-article-rsv (mail-header-number gnus-tmp-header)) (0) (100) 71 (nnir-article-group (mail-header-number gnus-tmp-header)) ("") (115) 103 (gnus-group-short-name (nnir-article-group ...)) ("") (115) (79 gnus-tmp-downloaded 99) (73 gnus-tmp-indentation 115) (84 (if ... "" ...) 115) (82 gnus-tmp-replied 99) (91 gnus-tmp-opening-bracket 99) (93 gnus-tmp-closing-bracket 99) (62 (make-string gnus-tmp-level 32) 115) ...] 41)
(defvar gnus-summary-line-format-alist (byte-code "...!.BB...!.BB........!.BB...!.BB.....!.BB...!.BB.......!.BB.BB....!.BB.BB....!.BB.BB......................!D.@.BB.&." [78 macroexpand ... ... 83 ... ... ... ... ... ... ... 120 ... ... 68 ... ... ... ... 77 ... ... 114 ... ... ... ... ... 90 or gnus-macroexpand-all ... ... ... 71 ... ... ... 103 ... ... ... ... ... ... ... ... ... ... ...] 41) ("/share/emacs/site-lisp/nognus-0.13/lisp/gnus-sum.elc" . 50944))
require(gnus-sum)
byte-code("..!...!...!...!...!...!." [require gnus gnus-int gnus-sum gnus-util nnmail easymenu] 2)
require(gnus-registry)
eval-buffer(#<buffer *load*> nil "/Users/ndw/.gnus" nil t) ; Reading at buffer position 412
load-with-code-conversion("/Users/ndw/.gnus" "/Users/ndw/.gnus" nil t)
load("~/.gnus" nil t)
gnus-read-init-file()
gnus-1(nil nil nil)
gnus(nil)
call-interactively(gnus t nil)
execute-extended-command(nil)
call-interactively(execute-extended-command nil nil)
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Don't despair, not even over the fact
http://nwalsh.com/ | that you don't despair.-- Kafka
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread* nnir is pwetty kewl! (Was: Recursive require with nognus?)
2011-03-18 14:02 ` Recursive require with nognus? Norman Walsh
@ 2011-03-18 18:42 ` Steinar Bang
2011-03-18 19:24 ` Norman Walsh
0 siblings, 1 reply; 21+ messages in thread
From: Steinar Bang @ 2011-03-18 18:42 UTC (permalink / raw)
To: ding
>>>>> Norman Walsh <ndw@nwalsh.com>:
> I don't think I'm trying to use nnir (it's not mentioned in my .gnus)
> so I'm not sure why this is only happening to me...
No config required on the new nnir.
But in case you get on top of your problems, see here for how to use
nnir on nnimap and gmane nntp groups:
http://thread.gmane.org/gmane.emacs.gnus.general/74430
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: nnir is pwetty kewl! (Was: Recursive require with nognus?)
2011-03-18 18:42 ` nnir is pwetty kewl! (Was: Recursive require with nognus?) Steinar Bang
@ 2011-03-18 19:24 ` Norman Walsh
2011-03-18 21:40 ` nnir is pwetty kewl! Steinar Bang
0 siblings, 1 reply; 21+ messages in thread
From: Norman Walsh @ 2011-03-18 19:24 UTC (permalink / raw)
To: ding
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
Steinar Bang <sb@dod.no> writes:
>>>>>> Norman Walsh <ndw@nwalsh.com>:
>
>> I don't think I'm trying to use nnir (it's not mentioned in my .gnus)
>> so I'm not sure why this is only happening to me...
>
> No config required on the new nnir.
>
> But in case you get on top of your problems, see here for how to use
> nnir on nnimap and gmane nntp groups:
> http://thread.gmane.org/gmane.emacs.gnus.general/74430
If I can ever get gnus past the circular dependency complaint... :-/
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Most human beings have an almost
http://nwalsh.com/ | infinite capacity for taking things for
| granted.--Aldous Huxley
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: nnir is pwetty kewl!
2011-03-18 19:24 ` Norman Walsh
@ 2011-03-18 21:40 ` Steinar Bang
2011-03-19 21:34 ` Norman Walsh
0 siblings, 1 reply; 21+ messages in thread
From: Steinar Bang @ 2011-03-18 21:40 UTC (permalink / raw)
To: ding
>>>>> Norman Walsh <ndw@nwalsh.com>:
> If I can ever get gnus past the circular dependency complaint... :-/
My approach is that I bisect my config until the issue go away. Ie. I
would start with removing the bottom half of my .emacs file and start
emacs and see if the issue went away. If it's still present I try again
with the top quarter of the original file, if it's gone, I try with the
top 3/4 of the file.
If all of .emacs is gone and the problem persist, I move on to
.gnus.el.
...or I start with .gnus.el. Whatever seems most appropriate.
(PS unless you version control your config, remember to make pristine
copies of the config files before starting)
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: nnir is pwetty kewl!
2011-03-18 21:40 ` nnir is pwetty kewl! Steinar Bang
@ 2011-03-19 21:34 ` Norman Walsh
2011-03-20 18:12 ` Steinar Bang
0 siblings, 1 reply; 21+ messages in thread
From: Norman Walsh @ 2011-03-19 21:34 UTC (permalink / raw)
To: ding
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
Steinar Bang <sb@dod.no> writes:
>>>>>> Norman Walsh <ndw@nwalsh.com>:
>
>> If I can ever get gnus past the circular dependency complaint... :-/
>
> My approach is that I bisect my config until the issue go away. Ie. I
> would start with removing the bottom half of my .emacs file and start
> emacs and see if the issue went away. If it's still present I try again
> with the top quarter of the original file, if it's gone, I try with the
> top 3/4 of the file.
Oh, sure, make me *work* for the answer :-)
<blush>Turns out I had an ancient version of nnir.el on my load-path.
Probably from trying it out in, uh, 2000 or thereabouts.</blush>
> (PS unless you version control your config, remember to make pristine
> copies of the config files before starting)
Egad! There are people in the twenty-first century who *don't* have
their config files under version control!?
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Where it is permissible both to die and
http://nwalsh.com/ | not to die, it is an abuse of valour to
| die.-- Mencius
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: nnir is pwetty kewl!
2011-03-19 21:34 ` Norman Walsh
@ 2011-03-20 18:12 ` Steinar Bang
0 siblings, 0 replies; 21+ messages in thread
From: Steinar Bang @ 2011-03-20 18:12 UTC (permalink / raw)
To: ding
>>>>> Norman Walsh <ndw@nwalsh.com>:
> <blush>Turns out I had an ancient version of nnir.el on my load-path.
> Probably from trying it out in, uh, 2000 or thereabouts.</blush>
Config bisecting is admittedly a crude way of debugging, but with (for
me) 22 years of accumulated emacs config, it's sometimes the only way.
Well, at least now you're ready to try the new nnir. If you do, you
won't be sorry. :-)
^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2011-03-20 18:12 UTC | newest]
Thread overview: 21+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-24 0:11 State of the art for HTML email Norman Walsh
2011-02-24 0:18 ` Edward O'Connor
2011-02-24 0:23 ` Norman Walsh
2011-02-24 23:08 ` Dave Goldberg
2011-02-25 15:46 ` Norman Walsh
2011-02-24 7:49 ` Reiner Steib
2011-02-24 11:42 ` Norman Walsh
2011-02-24 7:58 ` Steinar Bang
2011-02-24 12:28 ` Lars Ingebrigtsen
2011-02-24 12:55 ` Recursive require with emacs24? Norman Walsh
2011-02-24 13:11 ` Steinar Bang
2011-02-25 3:39 ` Lars Ingebrigtsen
2011-02-25 15:19 ` Norman Walsh
2011-03-05 12:07 ` Lars Magne Ingebrigtsen
2011-03-05 17:02 ` Andreas Schwab
2011-03-18 14:02 ` Recursive require with nognus? Norman Walsh
2011-03-18 18:42 ` nnir is pwetty kewl! (Was: Recursive require with nognus?) Steinar Bang
2011-03-18 19:24 ` Norman Walsh
2011-03-18 21:40 ` nnir is pwetty kewl! Steinar Bang
2011-03-19 21:34 ` Norman Walsh
2011-03-20 18:12 ` Steinar Bang
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).