Re: Send Bug Report is worse
On 3 Apr 2006, at 15:29, Jason Rumney wrote:
David Reitter wrote:
Lennart Borgman proposed to do this on Windows systems. That's
because apparently, long mailto:// URLs aren't supported well.
Lennart, do you think we can be more specific here and only enable
it when it's really needed, e.g. on old Windows installations?
I don't think the need for this is limited to old installations.
Windows has a 1024 byte limit to command-lines in general AFAIK.
OK, the limitation is due to ShellExecute (which is what's obviously
used on Windows, see `w32-shell-execute').
The mailto:// business in mailclient is a kludge, lacking a cross-
platform API.
The correct way to send an e-mail on Windows would be the mail API
("MAPI").
There is already an implementation of this available, even though
goes through Visual Basic:
http://www.emacswiki.org/cgi-bin/wiki/w32-send-mapi.el
One could take such a piece of code and implement an interface on the
C side to avoid the VB script. We could integrate that with
mailclient, and everyone would be happy.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Send Bug Report is worse
Jason Rumney wrote: David Reitter wrote: Lennart Borgman proposed to do this on Windows systems. That's because apparently, long mailto:// URLs aren't supported well. Lennart, do you think we can be more specific here and only enable it when it's really needed, e.g. on old Windows installations? I don't think the need for this is limited to old installations. Windows has a 1024 byte limit to command-lines in general AFAIK. Are you aware of that this includes the body too (body=...). It is even url encoded. I think there is quite a good chance that the mail url is bigger than 1024 bytes. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Send Bug Report is worse
David Reitter wrote: Lennart Borgman proposed to do this on Windows systems. That's because apparently, long mailto:// URLs aren't supported well. Lennart, do you think we can be more specific here and only enable it when it's really needed, e.g. on old Windows installations? I don't think the need for this is limited to old installations. Windows has a 1024 byte limit to command-lines in general AFAIK. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Send Bug Report is worse
On 3 Apr 2006, at 08:48, Reiner Steib wrote: On Mon, Apr 03 2006, Richard Stallman wrote: This message: "*** E-Mail body has been placed on clipboard, please paste them here! ***" I don't see that message when I use it. It must be specific to some aspect of your configuration. Where does it come from? The message comes from `mailclient-send-it' which is the default `send-mail-function' on some platforms: This method of transferring the body to the mail client is (by default) only used on Windows, where the default of `mailclient-place- body-on-clipboard-flag' is non-nil. http://lists.gnu.org/archive/html/emacs-devel/2005-08/msg00660.html Lennart Borgman proposed to do this on Windows systems. That's because apparently, long mailto:// URLs aren't supported well. Lennart, do you think we can be more specific here and only enable it when it's really needed, e.g. on old Windows installations? I agree the message needs to be revised syntactically, I'll do that when improving the default for `mailclient-place-body-on-clipboard- flag'. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Send Bug Report is worse
On Mon, Apr 03 2006, Richard Stallman wrote: > This message: > > "*** E-Mail body has been placed on clipboard, please paste > them here! ***" > > I don't see that message when I use it. It must be specific to some > aspect of your configuration. Where does it come from? The message comes from `mailclient-send-it' which is the default `send-mail-function' on some platforms: (defcustom send-mail-function (if (and window-system (memq system-type '(darwin windows-nt))) 'mailclient-send-it 'sendmail-send-it) "Function to call to send the current buffer as mail. [...]) `mailclient-send-it' tries to delegate the mail message to the system's default mail client. There have been suggestions to improve the message during a related discussion about `message-send-mail-function' on emacs-devel. (Cc-ing David Reitter, the author of `mailclient.el') Bye, Reiner. [1] See subject "gnus / message-send-mail-with-mailclient" in March. http://thread.gmane.org/[EMAIL PROTECTED] -- ,,, (o o) ---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/ ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Send Bug Report is worse
I do not understand you. What message are you talking about? How about if you show us the message you mean? This message: "*** E-Mail body has been placed on clipboard, please paste them here! ***" I don't see that message when I use it. It must be specific to some aspect of your configuration. Where does it come from? It is unnecessarily confusing. Put all of the instructions together, up front, before the place where the user types his bug report. What do others think? When you hit `C-c C-c', Send Bug Report "cleverly pastes...". I do not understand you. 6. Your email client opens a new mail message with "To: [EMAIL PROTECTED]" and "Subject: my bug report". The body of the message is "*** E-Mail body has been placed on clipboard, please paste them here! ***". That does not happen when I try it. If you had simply tried Send Bug Report, I think you would have been able to understand my report. Is it clear now? It is clear to me you are talking about something that doesn't happen when I try it. It must be specific to some aspect of your configuration. Please give a _complete_ test case! ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: Send Bug Report is worse
1. It's good that it now uses the user's mail client. It's
silly that it pastes a message saying to paste the message
you have already composed into the mail body. If the program
can paste this silly message then it can paste the message
that you have composed, and save you the trouble.
I do not understand you. What message are you talking about?
How about if you show us the message you mean?
This message:
"*** E-Mail body has been placed on clipboard, please paste them here! ***"
That message (and only that message) is automatically pasted by Send Bug
Report into an email message for you to send to emacs-pretest. BTW, the
message is also incorrect grammatically ("body" != "them").
2. The message-composition buffer, *mail*, has this text *following*
the cursor, so it ends up between the user's message and the extra
data that is to be sent:
What is wrong with that?
By "this text", I meant the paragraph that begins "If emacs crashed...".
IOW, first there are instructions, then the cursor (so, the user
message), then more instructions, then the session data
Yes, so what?
It is unnecessarily confusing. Put all of the instructions together, up
front, before the place where the user types his bug report.
The program cleverly pastes only the user's message
plus the data, avoiding this extra instruction.
What are you talking about? What is "the program"?
When you hit `C-c C-c', Send Bug Report "cleverly pastes...". IOW, although
this paragraph of instructions appears between your report text and the
additional text that is automatically sent, this paragraph is not sent
(which is good). Here is the order in buffer *mail*:
1. instructions
2. text you input for your email report
3. crash instructions
4. text (data) that is also included in your email
I'm saying that it would be clearer to keep 1&2 together in the buffer (they
are both instructions) and 3&4 together (they are both part of the email
that you send. That's all.
Please provide a precise test case.
1. emacs -Q
2. Help > Send Bug Report...
3. Enter a bug subject "my bug report" RET.
4. Type "abc" at the cursor in buffer *mail*. This is your bug-report text.
5. Hit `C-c C-c'. Type "yes" to confirm.
6. Your email client opens a new mail message with "To:
[EMAIL PROTECTED]" and "Subject: my bug report". The body of the message
is "*** E-Mail body has been placed on clipboard, please paste them here!
***".
7. You must select the message in the body, then use `C-v' (or whatever your
client uses for pasting) to paste your real message ("abc") into the body.
My point is that Send Bug Report should just paste your text ("abc") into
the message body, instead of pasting a message that tells you to paste your
message.
If you had simply tried Send Bug Report, I think you would have been able to
understand my report. Is it clear now?
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Send Bug Report is worse
"Drew Adams" <[EMAIL PROTECTED]> writes: > Help > Send Bug Report is worse than before. > > 1. It's good that it now uses the user's mail client. It's silly that > it pastes a message saying to paste the message you have already > composed into the mail body. If the program can paste this silly > message then it can paste the message that you have composed, and save > you the trouble. Not necessarily. If it is sending the message body to your mail client on the command-line, then there may be limits on the length that can be sent. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Send Bug Report is worse
1. It's good that it now uses the user's mail client. It's silly that it pastes a message saying to paste the message you have already composed into the mail body. If the program can paste this silly message then it can paste the message that you have composed, and save you the trouble. I do not understand you. What message are you talking about? How about if you show us the message you mean? 2. The message-composition buffer, *mail*, has this text *following* the cursor, so it ends up between the user's message and the extra data that is to be sent: What is wrong with that? IOW, first there are instructions, then the cursor (so, the user message), then more instructions, then the session data Yes, so what? The program cleverly pastes only the user's message plus the data, avoiding this extra instruction. What are you talking about? What is "the program"? Please provide a precise test case. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Send Bug Report is worse
Help > Send Bug Report is worse than before. 1. It's good that it now uses the user's mail client. It's silly that it pastes a message saying to paste the message you have already composed into the mail body. If the program can paste this silly message then it can paste the message that you have composed, and save you the trouble. 2. The message-composition buffer, *mail*, has this text *following* the cursor, so it ends up between the user's message and the extra data that is to be sent: "If emacs crashed, and you have the emacs process in the gdb debugger, please include the output from the following gdb commands: `bt full' and `xbacktrace'. If you would like to further debug the crash, please read the file c:/Emacs-22-2006-03-20/etc/DEBUG for instructions." IOW, first there are instructions, then the cursor (so, the user message), then more instructions, then the session data. The program cleverly pastes only the user's message plus the data, avoiding this extra instruction. All of the instructions should appear at the beginning. The user input area should be delineated by a horizontal line before and after. 3. There is no need for four colors for the header labels: black, blue, brown, red. What's the point? In GNU Emacs 22.0.50.1 (i386-mingw-nt5.1.2600) of 2006-03-20 on W2ONE X server distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4) --cflags -Id:/g/include' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: ENU locale-coding-system: cp1252 default-enable-multibyte-characters: t Major mode: Help Minor modes in effect: encoded-kbd-mode: t tooltip-mode: t auto-compression-mode: t tool-bar-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t unify-8859-on-encoding-mode: t utf-translate-cjk-mode: t line-number-mode: t view-mode: t Recent input: C-c C-c y e s Recent messages: Loading emacsbug...done Auto-saving...done Auto-saving...done Mark set Auto-saving...done Auto-saving...done Sending... Loading mailclient...done Loading browse-url...done Sending...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
