6

While wanting to start gitg as backgrounded through writing gitg & I accidentally typed gitg ¬. This did not cause an error, instead I got with a later command in the same terminal (translated): [1]+ Finished gitg

I am not sure if the two things were related. Anyway: Does anybody know what <programm> ¬ will do?

2
  • under ¬ you mean symbol or hitting return (enter)
    – MolbOrg
    Apr 16, 2014 at 14:58
  • @MolbOrg I mean I accidentally hit the strange ¬ symbol (of cause I send the command with enter, afterwards)
    – aldorado
    Apr 16, 2014 at 16:09

2 Answers 2

Reset to default
14

It will do nothing as far as I know. The ¬ will just be treated as an argument to the command:

$ ls ¬
ls: cannot access ¬: No such file or directory
5

In your case it printed previous backgrounded job result

[xxx@host]$ /usr/bin/echo test>/dev/null & <Enter>
[1] 4559
[xxx@host]$ <Enter>
[1]+  Done                    /usr/bin/echo test > /dev/null
5
  • This is correct - at least about what happened the first time - the process was backgrounded and the shell later reported when it quit.
    – mikeserv
    Apr 16, 2014 at 15:03
  • @mike actually process is gone long before second enter, which in that case acts like NOP, and after second command bash printed result of previous command. First second - i feel i missing point - can you clear it ?)
    – MolbOrg
    Apr 16, 2014 at 15:10
  • His gitg actually did bg is all i was saying. Whether or not that would happen again with the little handgun character i dont know, but it did the first time.
    – mikeserv
    Apr 16, 2014 at 15:12
  • @mike yes, sure - exactly)
    – MolbOrg
    Apr 16, 2014 at 15:13
  • Actually I repeated the gitg & command after realizing I used the wrong command. So that would be the explanation. Thanks!
    – aldorado
    Apr 16, 2014 at 16:06

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .