Bug 89462 – vim-X11 should include a gvimdiff symbolic link

Bug 89462 - vim-X11 should include a gvimdiff symbolic link

Summary:	vim-X11 should include a gvimdiff symbolic link

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	vim (Show other bugs)
Sub Component:
Version:	9
Hardware:	i386 Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Karsten Hopp
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-04-23 00:13 EDT by Todd J Martin
Modified:	2007-04-18 12:53 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-04-23 07:33:59 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Todd J Martin 2003-04-23 00:13:59 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
vim-enhanced-6.1-29 includes a vimdiff symbolic link to the vim executable. 
When vim is called like this, it automatically opens in diff mode.  Gvim has a
similar behavior if it is called by the name of gvimdiff.  Unfortunately, the
gvimdiff symbolic link never gets created.  Gvim is already compiled with diff
mode enabled.  All it needs is a symbolic link.

Version-Release number of selected component (if applicable):
vim-X11-6.1-29

How reproducible:
Always

Steps to Reproduce:
1. Run gvimdiff


Actual Results:  
[todd@perl etc]$ gvimdiff DIR_COLORS DIR_COLORS.rpmnew
bash2: gvimdiff: command not found
[todd@perl etc]$

Expected Results:  Gvim starts up in diff mode

Additional info:

Easy workaround is to do:

ln -s gvim gvimdiff

from the /usr/X11R6/bin directory.

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