After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 90594 - Implicit user editor spawn on composing
Implicit user editor spawn on composing
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
unspecified
Other All
: Normal enhancement
: 1.0
Assigned To: Charles Kerr
Pan QA Team
Depends on:
Blocks:
 
 
Reported: 2002-08-13 00:51 UTC by Gauze
Modified: 2007-05-23 00:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
A patch for this; provides a checkbox in the prefs; perhaps a little ghetto :-) (1.44 KB, patch)
2003-09-02 03:02 UTC, Benjamin Esham
none Details | Review

Description Gauze 2002-08-13 00:51:32 UTC
I would like to be able to use my editor of choice without having to cleeck
zee leetle button everytime I reply or compose a message. Gimme a check box.
Comment 1 Charles Kerr 2002-08-13 04:24:40 UTC
I like this idea.
Comment 2 Benjamin Esham 2003-09-02 03:02:01 UTC
Created attachment 19652 [details] [review]
A patch for this; provides a checkbox in the prefs; perhaps a little ghetto :-)
Comment 3 Owen Marshall 2004-01-22 00:24:35 UTC
Hmm, patched on 0.14.2. I don't even see the external editor working.
This is not fallout, as it doesn't seem to work on vanilla 0.14.2.

Why is this? I am calling `gvim %t' and get nothing but a blank file
each time. I make changes, but Pan ignores this.

Other than that, the patch seems to work(!). In my case, I see the
external editor first, and it is instantly covered up by pan's compose
window. Perhaps the simple method is to fire the window creation call
after the compose window comes on... but I haven't even glanced at the
code ;-)
Comment 4 Malte 2005-01-17 17:21:41 UTC
Owen Marshall> I don't even see the external editor working.

Same for me: I'm doing the same (gvim %t), and I get a blank file, and Pan
ignores changes. Using Pan 0.14.2.91 from Debian sarge.

I haven't tried the patch, though.
Comment 5 Charles Kerr 2007-01-22 17:35:51 UTC
Probably the editor window should be brought up in an idle function
after the post window has been realized, so that the sequencing will
be correct...
Comment 6 Michael Ekstrand 2007-03-23 01:00:22 UTC
By default, gvim detaches itself from its controller upon start.  You can do `gvim -f %t' to get around this, see if that clears up the blank file issue.
Comment 7 SciFi 2007-03-28 11:00:22 UTC
Hi,

For OSX users wanting to use TextWrangler or BBEdit natively as your pan2 editor here, insert this line in your posting.xml file inside the <editor> section:

    <editor active="true">edit -w</editor>

Beforehand, be sure to tell TextWrangler or BBEdit to install its imbedded unix tools, this will add the 'edit' command to your system (you only need to do this once).

The '-w' is to tell Pan to wait for you to save & close the window (finish editing), then the text will get plopped into the Pan posting window.

While you're editing, you can use the spell-check feature and any other gizmos that are available as a normal OSX app.  You can open other documents, copy-&-paste between other editor windows & even other apps, etc. etc. etc.

One thing that Pan needs here, tho, is to use a separate thread for the posting window, so other things such as downloads can continue on while editing.

Thanks...   :)