|
|
Up |
|
|
  |
Author: AlanAlan
Date: Dec 26, 2008 11:19
On October 3, 2008 I made a posting that said:
"XEmacs will become often become completely unresponsive under
circumstances that are similar to what I describe below:"
and it described a problem with using VM together with a VPN
connection, with a PC running Windows XP Home.
Recent experience is that this hasn't happened if I am careful to make
sure that XEmacs is started after the VPN connection is made.
The astute reader will also note that my XEmacs version is now 21.4.21
and the older posting was for 21.4.20. My full version info is:
XEmacs 21.4 (patch 21) "Educational Television" [Lucid] (i586-pc-
win32) of Sun Oct 07 2007 on VSHELTON-PC2
|
| |
|
| |
no comments
|
|
  |
Author: Giacomo BoffiGiacomo Boffi
Date: Sep 22, 2008 01:48
Dear Gentlemen,
some correspondents of mine have a bizarre pleasure in attaching MS
WORD documents whose filenames contain spaces to their emails
i know for sure that i can make VM protect these filenames before
passing them to openoffice[*], but i don't know what to do exactly...
i will overly appreciate any help
yours
gb
[*] openoffice, when passed filenames containing unprotected spaces,
barks "no such file 'I'", "no such file 'have'", "no such file 'troubles'",
and so on and so on
--
la lenza penzola
-- PMF, in IHC
|
| |
|
| |
no comments
|
|
  |
Author: howcomehowcome
Date: Sep 10, 2008 02:12
I use vm 8.0.11 on gnu emacs 22.1.1.
When receiving email with slightly exotic charsets, vm often switches
to an even more exotic charset in the reply (namely iso-2022-jp). For
example, when the incoming message is in iso-8859-15 and contains the
letter "å", the reply will be in iso-2022-jp and appear mangled.
I've seen this problem in the past as well, with various suggested
fixes. However, I think vm itself should fix this.
What do other people do?
|
| |
|
1 Comment |
|
  |
Author: Aidan KehoeAidan Kehoe
Date: Aug 22, 2008 10:48
This checks for some MIME character sets available in recent XEmacs.
2008-08-22 Aidan Kehoe parhasard.net>
* lisp/vm-mime.el (vm-update-mime-charset-maps):
Check for some MIME character sets that may be available in recent
XEmacs.
diff -r 98c2b48485d8 -r 241b44b23516 xemacs-packages/vm/lisp/vm-mime.el
--- a/xemacs-packages/vm/lisp/vm-mime.el Fri Aug 22 19:39:50 2008 +0200
+++ b/xemacs-packages/vm/lisp/vm-mime.el Fri Aug 22 19:43:09 2008 +0200
@@ -95,7 +95,10 @@
vm-mime-mule-charset-to-coding-alist))
(add-to-list 'vm-mime-mule-charset-to-coding-alist
(list (format "%%s" x) x)))))
- '(utf-8 iso-8859-15 iso-8859-14 iso-8859-16))
+ '(utf-8 iso-8859-15 iso-8859-14 iso-8859-16
+ alternativnyj iso-8859-6 iso-8859-7 koi8-c koi8-o koi8-ru koi8-t
+ koi8-u macintosh windows-1250 windows-1251 windows-1252
+ windows-1253 windows-1256))
;; And make sure that the map back from coding-systems is good for
;; those charsets.
|
| Show full article (1.15Kb) |
|
no comments
|
|
  |
Author: Aidan KehoeAidan Kehoe
Date: Aug 21, 2008 10:43
Hi Robert,
The following code, executed on an XEmacs 21.5-b28 -vanilla, gives me an
infinite loop:
(progn
(load "vm")
(load "vm-mime")
(load "vm-misc")
(vm-mime-encode-words-in-string
"\u1D1B\u1D0F\u0274"))
The issue is that #'encode-coding-region messes around with the markers
under XEmacs, though not under current GNU. Kyle has already worked around
this in other places, and this change to #'vm-mime-encode-words fixes the
issue for me:
|
| Show full article (1.09Kb) |
|
no comments
|
|
  |
Author: Aidan KehoeAidan Kehoe
Date: Aug 20, 2008 09:10
Hi Robert --
Here’s a backtrace I get when I try to do vm-visit-folder in a Carbon build
of XEmacs (from the sources at http://hg.debian.org/hg/xemacs/xemacs-carbon2
). I’m not sure what’s going wrong; it may well be an issue in the
platform-specific code. I happen to be on holiday, so I’ll see can I solve
this in the next few days.
Debugger entered--Lisp error: (invalid-operation "Window height too small (after splitting)" 0)
split-window(# 0 nil)
tapestry-apply-window-map((- (0 0 80 10) (0 10...
|
| Show full article (5.47Kb) |
|
1 Comment |
|
  |
|
|
  |
Author: h20mysticshadowh20mysticshadow
Date: Aug 11, 2008 05:02
Comprehensive list of industrial property for rent, commercial real
estate for rent, commercial for rent, commercial real estate
industrial, industrial commercial property in Australia
Contact us @ http://realestate.ozfreeonline.com/
searchlistings/For-Rent/Commercial-Industrial-sale">commercial real
estate for more details!
|
| |
|
no comments
|
|
  |
Author: tfttft
Date: Aug 3, 2008 01:40
I did a 'VM homepage' google search and couldn't land on the current
homepage [1] which forced me to scour gnu.org to find it. Gnu.org
forwarded me to fsf which listed the old info (maintainer, homepage,
etc) which needs to be updated.
http://directory.fsf.org/project/vm/
I'd highly recommend adding a "keywords" meta tag to the current VM
homepage to include the string 'VM' among others. Consider also
modifying the title to ' View Mail (aka VM) for Emacs' (note addition
of VM in there).
[1] http://www.nongnu.org/viewmail/
Regards,
.tf.
|
| |
|
1 Comment |
|
  |
|
|
  |
Author: tylertyler
Date: Jul 28, 2008 11:36
Hi,
I'm trying to run vm on GNU Emacs 23.0.60.1 (build from CVS sources,
running on Debian Lenny). I downloaded and installed vm-8.0.10-575,
created a new directory ~/vm, made a copy of my current inbox there for
testing, and put (setq vm-primary-inbox "~/vm/inbox") in ~/.vm
M-x vm opens a buffer that displays the headers for the
first message in the inbox, but no message body. I can scroll through
the messages using n and p, but I never see a message body. I can't see
a summary of the folder, although my buffer list shows 'inbox Summary' and
'inbox Presentation' in addition to 'inbox'. Trying to switch into these
buffers does nothing - i.e., C-x b, select inbox Summary, nothing
happens, I'm left with the same buffers visible in the current windows.
Any suggestions?
Thanks,
Tyler
--
What is wanted is not the will to believe, but the will to find out, which is
the exact opposite. --Bertrand Russell
|
| |
|
3 Comments |
|
|
|
|