Language Selection

English French German Italian Portuguese Spanish

Search Next or Backwards and Goto Line Tips for VIM

Filed under
HowTos

To search in vim is very simple, even a noob vim user know that,

/keyword

To search for next?

simply follow by pressing n for next keyword match point and search backward with shift+n or N.

Wanna highlight the keyword and search for next keyword match point?
Place your cursor at the desire word, and press shift 8(8 not at number pad) or *.

To highlight the keyword search?

Full Story.

Gobbeldy Schmockel

Just as I suspected. Vi advocates cannot communicate with humans:

Quote:
even a noob vim user know that

Quote:
Place your cursor at the desire word

Quote:
While opening the file sample.cc, I wanna goto line 165, which originally mention at here before.

Of course, you know why they cannot communicate and why man pages are so hard to decipher? It's because the writers are using vi.

When every fibre of your being is focussed on remembering key bindings, how can you even begin to think about what you are writing?

For seekers only

re: Gobbeldy Schmockel

Quote:

When every fibre of your being is focussed on remembering key bindings, how can you even begin to think about what you are writing?

teehee! I often shutter at some of the grammer mistakes I see in some of the posts I link to and there are times they are so thick you can barely make out what the 'author' is trying to say. I try not to make too many myself, but there isn't an article written by me in which I'm not still finding mistakes. Writing is harder than it looks. Big Grin

Vi was the first terminal editor I learned. In fact, it's probably the only console editor I learned. I still use it for quick config file edits. I never learned all (or even most) of the key-bindings. I learned enough to do quick edits. I write my stories in kwrite. I like it because it is a bit more primitive than some of the others, with the main advantage being it doesn't code the line breaks like even Vi does. But I still like Vi for those quick edits.

In fact, I believe everyone should learn the few commands needed to use Vi for editing. There are still a few distros out there that only ship with Vi. What if you needed to edit the xorg.conf file to get into X and Vi is all that's available?

----
You talk the talk, but do you waddle the waddle?

The early pioneer days are over

- get used to it

Quote:
There are still a few distros out there that only ship with Vi. What if you needed to edit the xorg.conf file to get into X and Vi is all that's available?

That's easy. I don't do distros which are that unevolved. Like I don't use software that's stuck in the '80s.

----
I try to take one day at a time -- but sometimes several days attack me at once - Ashleigh Brilliant

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Android Leftovers

Today in Techrights

Fedora: Anaconda Improvements, Greenboot, Fedora Scientific Vagrant Boxes and Abhishek

  • Anaconda improvements in Fedora 28
    Fedora 28 was released last month, and the major update brought with it a raft of new features for the Fedora Installer (Anaconda). Like Fedora, Anaconda is a dynamic software project with new features and updates every release. Some changes are user visible, while others happen under the hood — making Anaconda more robust and prepared for future improvements.
  • Lorbus: Introducing: greenboot
    Not too long ago, I applied to Google Summer of Code for the student scholarship position together with a Fedora project ideated by Peter Robinson, who is the principal IoT architect at Red Hat, named Fedora IoT: Atomic Host Upgrade Daemon. As you may be guessing by now, I was very fortunate and the proposal was accepted! The coding phase started on the 14th of May and in this blog post I’ll try to give a little insight into my first month working on the project.
  • Pre-release Fedora Scientific Vagrant Boxes
    I am very excited to share that sometime back the Fedora project gave the go ahead on my idea of making Fedora Scientific available as Vagrant boxes starting with Fedora 29. This basically means (I think) that using Fedora Scientific in a virtual machine is even easier.
  • [Week 5] GSoC Status Report for Fedora App: Abhishek

Red Hat News

  • An Open Source Load Balancer for OpenShift
    A highly-available deployment of OpenShift needs at least two load balancers: One to load balance the control plane (the master API endpoints) and one for the data plane (the application routers). In most on-premise deployments, we use appliance-based load balancers (such as F5 or Netscaler).
  • Red Hat Beefs Up Platform as a Service Suite
    Red Hat has begun shipping Red Hat Fuse 7, the next major release of its distributed, cloud-native integration solution, and introduced a new fully hosted low-code integration platform as a service (iPaaS) offering, Fuse Online. With Fuse 7, the vendor says expanding its integration capabilities natively to Red Hat OpenShift Container Platform, an enterprise Kubernetes platform. Fuse gives customers a unified solution for creating, extending and deploying containerized integration services across hybrid cloud environments.
  • Red Hat ‘Fuses’ Low Code Development and Data Integration
    Red Hat, a provider of open source solutions, has announced Red Hat Fuse 7, the next major release of its distributed, cloud-native integration solution, and introduced a new fully hosted low-code integration platform as a service offering, Fuse Online. With Fuse 7, Red Hat is expanding its integration capabilities natively to Red Hat OpenShift Container Platform, a comprehensive enterprise Kubernetes platform. Fuse gives customers a unified solution for creating, extending and deploying containerized integration services across hybrid cloud environments.
  • The GPL cooperation commitment and Red Hat projects
    As of today, all new Red Hat-initiated open source projects that opt to use GPLv2 or LGPLv2.1 will be expected to supplement the license with the cure commitment language of GPLv3. The cure language will live in a file in the project source tree and will function as an additional permission extended to users from the start. This is the latest development in an ongoing initiative within the open source community to promote predictability and stability in enforcement of GPL-family licenses. The “automatic termination” provision in GPLv2 and LGPLv2.x is often interpreted as terminating the license upon noncompliance without a grace period or other opportunity to correct the error in compliance. When the Free Software Foundation released GPLv2 in 1991, it held nearly all GPL-licensed copyrights, in part a consequence of the copyright assignment policy then in place for GNU project contributions. Long after the Linux kernel and many other non-GNU projects began to adopt the GPL and LGPL, the FSF was still the only copyright holder regularly engaged in license enforcement. Under those conditions, the automatic termination feature of GPLv2 section 4 may have seemed an appropriate means of encouraging license compliance.
  • Monness Believes Red Hat (NYSE: RHT) Still Has Room to Grow
  • Comparing Red Hat (RHT) & Autoweb (AUTO)
  • As Red Hat (RHT) Share Value Rose, Calamos Advisors Upped Its Position by $300,831; Chilton Capital Management Increases Stake in Equinix (EQIX)
  • Blair William & Co. IL Buys 23,279 Shares of Red Hat Inc (RHT)