Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
5
Newest
 Scholar
Impact
~1k people reached

  • 0 posts edited
  • 1 helpful flag
  • 29 votes cast
May
23
comment Blocking Start of Terminal
Re: 1, indeed, but my application is providing compatibility, not demanding it (my application actually also explicitly supports xterm, rxvt, and terminator, among others, already). Re: 2, +1 this is a neat idea, and it forms the basis of the accepted answer. Though simpler, I think waiting on the process ID is a better and safe(r) idea. Thanks!
May
23
accepted Blocking Start of Terminal
May
22
comment Blocking Start of Terminal
I am aware. You, terdon, and ecatmur all have +1s, and after some more time has elapsed, I will accept the best. Currently yours.
May
22
comment Blocking Start of Terminal
I've forked it into its own question.
May
22
comment Blocking Start of Terminal
I agree, but if such a thing exists, it would have ~same latency as the scheduler (probably less than whatever delay you might reasonably put) and use less CPU than busy looping like in terdon's answer.
May
22
comment Blocking Start of Terminal
I like that this is safe(r) than @terdon's current answer, which is similar. I don't suppose Bash has a thread yield one could use instead of sleep?
May
22
comment Blocking Start of Terminal
+1 for finding the bug, suggesting the fix, and pushing it upstream. Unfortunately, my application needs to work with vanilla builds and be backward compatible (and in any case it doesn't solve the problem for lxterminal &tc., which I was unofficially also asking about).
May
22
comment Blocking Start of Terminal
Yes. Unfortunately that command doesn't have the desired effect since gnome-terminal starts a terminal asynchronously, returning immediately.
May
22
comment Blocking Start of Terminal
Thanks for the answer, but I actually want precisely the opposite. On my system, gnome-terminal is implemented as a Python script that opens the terminal asynchronously already. xterm might be basic enough to reproduce the behavior I want.
May
22
comment Blocking Start of Terminal
@ByteCommander, yes; exactly.¶ Serg: indeed it is dated. That's the point.
May
22
asked Blocking Start of Terminal
May
15
awarded  Scholar
May
15
accepted Why Can't GrUB Find a Kernel That It Already Found?
May
15
awarded  Commentator
May
15
comment Why Can't GrUB Find a Kernel That It Already Found?
@saiarcot895 after installing GrUB 2, redoing your (n-2)nd comment, and then rebooting, it boots into 3.19. If you repost the above and also explain what 0.97's problem was, that sounds like an answer!
May
15
comment Why Can't GrUB Find a Kernel That It Already Found?
@saiarcot895 I do not have it installed. As tagged above, the GrUB version is 0.97. Do you think should upgrade to GrUB 2?
May
15
comment Why Can't GrUB Find a Kernel That It Already Found?
@saiarcot895 done. It does not.
May
15
comment Why Can't GrUB Find a Kernel That It Already Found?
@saiarcot895 linux-image-3.19.0-17-generic is also present in the dpkg listing. I do have a grub.cfg file, and it indeed lacks the 3.19 record.
May
15
comment Kernel Headers for Ubuntu 15.04
@saiarcot895 I have forked it into a separate question.
May
15
asked Why Can't GrUB Find a Kernel That It Already Found?