36

When you do shift-f with less, you can see the file update in real time, and you get the "Waiting for data...(interrupt to abort)" message.

The updating works fine, but what is the interrupt? nothing seems to work (Ctrl-C, Esc, Ctrl-I etc). I always have to kill the terminal which is a pain.

Improve this question
2
  • 2
    For me, interrupt (ctrl-c) works fine, except that it kills the whole process!
    – taranaki
    Mar 31, 2017 at 17:39
  • SHIFT + CNTRL + C works for me to interrupt without totally killing less
    – bbartling
    Jun 11 at 18:54

6 Answers 6

Reset to default
33

Ctrl+C works for me. When I use the F command in less, it says "(interrupt to abort)". The "interrupt" that it's referring to is whatever key is bound to the terminal interrupt. The command stty -a shows the relevant terminal settings:

speed 38400 baud; rows 50; columns 80; line = 0; intr = ^C; quit = ^; erase = ^H; kill = ^U; eof = ^D; eol = ; eol2 = ; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxbel -iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke

It's the intr = ^C that shows that interrupt is generated by Ctrl+C.

If you do stty -a what does it show?

Improve this answer
5
  • 1
    it says intr = ^C. Aha!! it's actually Ctrl-shift-c - ie upper case. Thanks for the help
    – Daniel
    Oct 25, 2009 at 13:05
  • 4
    That's weird - I've never known Ctrl+Shift to be different from just Ctrl. Mine shows upper case C, but Ctrl+c (without shift) works fine.
    – Randy Orrison
    Oct 25, 2009 at 13:21
  • 5
    I've never used a system that treated ctrl-c and ctrl-C differently, either. Just a data point.
    – CarlF
    Oct 25, 2009 at 13:45
  • 1
    I'm having the same issue, and neither ctrl-c nor ctrl-shift-c works. Could this have something to do with the fact that i'm running less inside a screen session?
    – jenming
    Dec 13, 2013 at 22:35
  • 2
    This works for me: 'ctrl-shift-c' switch to normal mode and simply enter q to quit
    – Mohammad Ali Akbari
    Mar 30, 2015 at 20:00
4

Ctrl + C did not work for me. However, I was able to stop the process with q.

Improve this answer
2

As @RandyOrrison mentioned, ^C (control + c) is the appropriate interrupt character. Although, how less responds to this signal will vary based on the options provided at execution time.

Normally, an interrupt character causes less to stop whatever it is doing and return to its command prompt (i.e. not the terminal/tty prompt).

If instead, you want to signal less to quit and return to the terminal/tty prompt, you should use the -K or --quit-on-intr option. This will cause less to exit immediately (with status 2) when an interrupt character (usually ^C) is typed.

less manpage

-K , --quit-on-intr

Causes less to exit immediately (with status 2) when an interrupt character (usually ^C) is typed. Normally, an interrupt character causes less to stop whatever it is doing and return to its command prompt. Note that use of this option makes it impossible to return to the command prompt from the "F" command.

less -K [filename]...
less --quit-on-intr [filename]...
Improve this answer
1

ctrl-C is closing the process at the head of the pipe, not signeling less, when using a pipeline like this.

head-process | less

I got it to work with:

less -f <(head-process)

There may be a better way.

Improve this answer
1
  • AFAIK the signal should get to less as well; "not signalling less" is somewhat surprising to me. About the solution: yeah. :)
    – Kamil Maciorowski
    Aug 13, 2021 at 22:04
-2

Try Shift + Ctrl + C, I had the same issue and needed to do Ctrl + Z -> fg -> Q to quit.

Improve this answer
1
  • There is no need to put less into background and resuming it with fg, before quitting. You could have pressed q right away.
    – dirdi
    Sep 27, 2019 at 12:43
-2

I was stuck in less with no argument over than the file I wanted to fast check from my terminal, Ctrl-c, Ctrl shift-c nothing worked. Ctrl-z did the job :)

Improve this answer
1
  • 2
    ^Z does not kill or quit less but stops and puts it into background for being resumed later. Therefore, this is not an answer to the question.
    – dirdi
    Sep 27, 2019 at 12:41

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy