Bug 84794 - Knode fails to open external editor (gvim) with message context
Knode fails to open external editor (gvim) with message context
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: vim (Show other bugs)
8.0
All Linux
medium Severity low
: ---
: ---
Assigned To: Karsten Hopp
David Lawrence
:
Depends On: 88169
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-21 09:16 EST by Scott R. Godin
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-04-07 08:24:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Scott R. Godin 2003-02-21 09:16:36 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
reply to a posted newsgroup message, and choose "Start external editor" from the
Tools menu.

Whether or not the message content is selected, it fails to appear in the
external editor's window and must be manually copy/pasted there.

This works fine with Gedit, but gvim does not seem to open the message content
in the editing window

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.open Knode Preferences and choose gvim as your external editor
2.open a newsgroup in knode, and select a message to reply to
3.in the reply window, choose "start external Editor"
4.bang head on keyboard when message content fails to appear in the gvim window
5. change external editor to gedit in knode preferences
6. repeat steps 2-3
7. message content appears in gedit window
8. grind teeth
    

Actual Results:  message content fails to appear in external gvim editor window

Expected Results:  message content appears in external gvim editor window and is
editable. 

Additional info:

I would have filed this against the 'knode' package rather than 'kdebase' but
one does not currently exist in bugzilla's package listing. I've filed a bug
against that as well. *sigh*
Comment 1 Ngo Than 2003-02-22 18:27:44 EST
It seems that gvim does remove all messages from the file.
Comment 2 Martin Norback 2003-04-07 07:46:45 EDT
I think this is because of the reason described in bug 88169
Comment 3 Karsten Hopp 2003-04-07 08:24:36 EDT
This is the expected behaviour of gvim. Workaround to disable forking is described in bug 
#88169 

Note You need to log in before you can comment on or make changes to this bug.