top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration

vi behavior on Fedora?

0 votes
24 views

I observe 2 different behaviors of vi that I cannot explain. 2 different machines, same distribution

On one machine when I underline some text with the mouse (not in append mode), vi turns to a VISUAL mode, and not in the other machine.

posted Jan 8, 2017 by Sheetal Chauhan

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button
Looks like the issue which was fixed in this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1401410

1 Answer

0 votes

I recently had a similar experience after I finished upgrading to F25 (vim version 8.x)

Now I either start vi in the following way:

vi -C 

(see vi --help for the explanations)

or if I have already started using vi with a particular file, I issue the following command:

:set mouse=

I seem to have more success w/ the former than the latter (YMMV).

answer Jan 8, 2017 by Sonu Jindal
Similar Questions
0 votes

Installed Fedora 26 on recommendation of a Scribus developer. Installed about 30 packages per his advice.

But when I try to compile a program the machine can't find C++. So what is the package I need to install to compile C++ programs?.

Another question. On Slackware (yes I am one of those) I can use kdm to get to a window function ( I preferXFCE). How do I set up a window manager in Fedora and how do I access it?

0 votes

Each time I turn off Fedora 24, I get the following message about 50 times printed in the console:

Kernel not configured for semaphores (System V IPC). Not using udev synchronisation code.
device-mapper: remove ioctl on fedora_alpha-root failed: Device or resource busy Command failed

What does that mean?

+1 vote

I'm running Fedora-24(beta)/KDE, and sendmail/email (through KMail) is failing.
When I try to send email I get the warning "Failed to transmit message", and journalctl has the entry
"sendmail.service: PID file /run/sendmail.pid not readable (yet?)
after start: No such file or directory".

I've checked, and sendmail.pid is in place:

$ sudo cat /run/sendmail.pid 
2829 
/usr/sbin/sendmail -bd -q1h 

Googling for the journalctl entry, I see people have been encountering this problem for years. But I haven't seen any solution offered. Several of the comments suggest that it is a systemd problem.

please help?

Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Bangalore-560102
Karnataka INDIA.
QUERY HOME
...