* Odd formatting (was: proposal to make null string handling more emacs-y) [not found] ` <CAGtm15ntnkSBNiLeSYCQ8OUm+oQNA0NqZxvqeT1TGwPJjjwqgw@mail.gmail.com> @ 2012-04-29 21:26 ` Lars Magne Ingebrigtsen 2012-04-30 7:48 ` Odd formatting Steinar Bang 0 siblings, 1 reply; 3+ messages in thread From: Lars Magne Ingebrigtsen @ 2012-04-29 21:26 UTC (permalink / raw) To: Steve Yegge; +Cc: ding, emacs-devel Steve Yegge <steve.yegge@gmail.com> writes: > I agree with you. Fortunately that's not what I'm arguing. I'm arguing > that > for a very specific corner of the type system, we merge two separate > meanings of nil. I'm arguing that the empty string as it is used today > is, > for all intents, just another nil. So it should not signal an error if > they are > treated the same. Totally off topic, I was looking at how strange your messages are rendering and wondering whether the mail reader was interpreting your messages incorrectly or something. But here's the (sort of) raw source of that text: <div>I agree with you. Fortunately that's not what I'm arguing. I'm arguing that</div><div>for a very specific corner of the type system, we merge two separate</div> <div>meanings of nil. I'm arguing that the empty string as it is used today is,</div><div>for all intents, just another nil. So it should not signal an error if they are</div><div>treated the same.</div> (This is the text/html part of the multipart message you send.) So your mail reader is wrapping (apparently) random parts of the text in <div> section, and <div> section are rendered by shr.el as a block-level elements (which is quite normal, I think). You're posting through Gmail, so I expect to see a lot more of this kind of stuff in the future. Does anybody know why Gmail is doing this, and what shr should be doing to this, er, stuff to render it properly? I can't see any hints in the source of the message that these <div>s are supposed to be non-block-level elements, but perhaps I'm missing something... -- (domestic pets only, the antidote for overdose, milk.) bloggy blog http://lars.ingebrigtsen.no/ ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Odd formatting 2012-04-29 21:26 ` Odd formatting (was: proposal to make null string handling more emacs-y) Lars Magne Ingebrigtsen @ 2012-04-30 7:48 ` Steinar Bang 2012-04-30 10:14 ` Antoine Levitt 0 siblings, 1 reply; 3+ messages in thread From: Steinar Bang @ 2012-04-30 7:48 UTC (permalink / raw) To: emacs-devel; +Cc: ding >>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>: > Totally off topic, I was looking at how strange your messages are > rendering and wondering whether the mail reader was interpreting your > messages incorrectly or something. But here's the (sort of) raw source > of that text: > <div>I agree with you. Fortunately that's not what I'm arguing. I'm arguing that</div><div>for a very specific corner of the type system, we merge two separate</div> > <div>meanings of nil. I'm arguing that the empty string as it is used today is,</div><div>for all intents, just another nil. So it should not signal an error if they are</div><div>treated the same.</div> > (This is the text/html part of the multipart message you send.) Note that the text/plain version of the message is foramatted exactly like the bit you quoted. ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Odd formatting 2012-04-30 7:48 ` Odd formatting Steinar Bang @ 2012-04-30 10:14 ` Antoine Levitt 0 siblings, 0 replies; 3+ messages in thread From: Antoine Levitt @ 2012-04-30 10:14 UTC (permalink / raw) To: emacs-devel; +Cc: ding 30/04/12 09:48, Steinar Bang >>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>: > >> Totally off topic, I was looking at how strange your messages are >> rendering and wondering whether the mail reader was interpreting your >> messages incorrectly or something. But here's the (sort of) raw source >> of that text: > >> <div>I agree with you. Fortunately that's not what I'm arguing. I'm arguing that</div><div>for a very specific corner of the type system, we merge two separate</div> >> <div>meanings of nil. I'm arguing that the empty string as it is used today is,</div><div>for all intents, just another nil. So it should not signal an error if they are</div><div>treated the same.</div> > >> (This is the text/html part of the multipart message you send.) > > Note that the text/plain version of the message is foramatted exactly > like the bit you quoted. Looks like he's writing his email in emacs, with emacs wrapping, and then pasting it into gmail, which then adds further (and different) wrapping. Not much gnus can do, I think. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-04-30 10:14 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <CAGtm15=Wb1Uv_WvYKQ7hMBkb=2Y1qUJjGnFFkBj6fcPotgXV8g@mail.gmail.com> [not found] ` <83d36wfcf1.fsf@gnu.org> [not found] ` <jwvwr53j3i9.fsf-monnier+emacs@gnu.org> [not found] ` <834ns7g9r8.fsf@gnu.org> [not found] ` <jwvliljj0er.fsf-monnier+emacs@gnu.org> [not found] ` <CAGtm15=gkeHkVQdau0ywcBC6tHVLF4pHYzVhDO5B4Nob23z_zg@mail.gmail.com> [not found] ` <jwv1unaf0e8.fsf-monnier+emacs@gnu.org> [not found] ` <CAGtm15=vkZ6K+Q246J4nx1rob_UjjQbwH_ZkrNJa7qdGr46jxQ@mail.gmail.com> [not found] ` <83zk9xheam.fsf@gnu.org> [not found] ` <CAGtm15ntnkSBNiLeSYCQ8OUm+oQNA0NqZxvqeT1TGwPJjjwqgw@mail.gmail.com> 2012-04-29 21:26 ` Odd formatting (was: proposal to make null string handling more emacs-y) Lars Magne Ingebrigtsen 2012-04-30 7:48 ` Odd formatting Steinar Bang 2012-04-30 10:14 ` Antoine Levitt
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).