sqlite3 command beeps whenever I press 'b' [closed]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
1
down vote

favorite












If I fire up sqlite and then, at the prompt, type the letters a to z followed by the digits 0 to 9, I see this:



$ sqlite3 
SQLite version 3.22.0 2018-01-22 18:45:57
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> acdefghijklmnopqrstuvwxyz0123456789


When I hit the b key, I get a beep, and no character is echoed to the sqlite prompt.



If I try and see what tables I get using the .tables command, I get this:



sqlite> .tales
Error: unknown command or invalid arguments: "tales". Enter ".help" for help


So it's not merely failing to echo it, but rather the b just never gets entered at the prompt at all.



Why does this happen? I'm sure I'll kick myself when I find out!



I'm using the stock sqlite from Ubuntu 18.04:



$ dpkg -S $(which sqlite3)
sqlite3: /usr/bin/sqlite3
$ dpkg -s sqlite3 | grep ^Version
Version: 3.22.0-1






share|improve this question











closed as off-topic by Thomas Dickey, slm♦ Jul 29 at 4:15


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Thomas Dickey, slm
If this question can be reworded to fit the rules in the help center, please edit the question.








  • 1




    Does ~/.inputrc exist?
    – Ignacio Vazquez-Abrams
    Jul 28 at 22:01










  • Yes! That was it! And I did mentally kick myself
    – Croad Langshan
    Jul 28 at 22:43










  • Not actually sure what's wrong with that file: $ cat ~/.inputrc bind \C-b:unix-filename-rubout
    – Croad Langshan
    Jul 28 at 22:45










  • This question has come up before, and seems to have been closed and then deleted, probably for the same reason as people want to close it now. This is a shame, because clearly it is a problem that can be reproduced, and has been by multiple people coming to StackExchange to report odd keys not working over the years.
    – JdeBP
    Jul 29 at 0:12










  • @JdeBP Probably a good candidate for a canonical duplicate target if you want to write one.
    – Michael Homer
    Jul 29 at 4:29
















up vote
1
down vote

favorite












If I fire up sqlite and then, at the prompt, type the letters a to z followed by the digits 0 to 9, I see this:



$ sqlite3 
SQLite version 3.22.0 2018-01-22 18:45:57
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> acdefghijklmnopqrstuvwxyz0123456789


When I hit the b key, I get a beep, and no character is echoed to the sqlite prompt.



If I try and see what tables I get using the .tables command, I get this:



sqlite> .tales
Error: unknown command or invalid arguments: "tales". Enter ".help" for help


So it's not merely failing to echo it, but rather the b just never gets entered at the prompt at all.



Why does this happen? I'm sure I'll kick myself when I find out!



I'm using the stock sqlite from Ubuntu 18.04:



$ dpkg -S $(which sqlite3)
sqlite3: /usr/bin/sqlite3
$ dpkg -s sqlite3 | grep ^Version
Version: 3.22.0-1






share|improve this question











closed as off-topic by Thomas Dickey, slm♦ Jul 29 at 4:15


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Thomas Dickey, slm
If this question can be reworded to fit the rules in the help center, please edit the question.








  • 1




    Does ~/.inputrc exist?
    – Ignacio Vazquez-Abrams
    Jul 28 at 22:01










  • Yes! That was it! And I did mentally kick myself
    – Croad Langshan
    Jul 28 at 22:43










  • Not actually sure what's wrong with that file: $ cat ~/.inputrc bind \C-b:unix-filename-rubout
    – Croad Langshan
    Jul 28 at 22:45










  • This question has come up before, and seems to have been closed and then deleted, probably for the same reason as people want to close it now. This is a shame, because clearly it is a problem that can be reproduced, and has been by multiple people coming to StackExchange to report odd keys not working over the years.
    – JdeBP
    Jul 29 at 0:12










  • @JdeBP Probably a good candidate for a canonical duplicate target if you want to write one.
    – Michael Homer
    Jul 29 at 4:29












up vote
1
down vote

favorite









up vote
1
down vote

favorite











If I fire up sqlite and then, at the prompt, type the letters a to z followed by the digits 0 to 9, I see this:



$ sqlite3 
SQLite version 3.22.0 2018-01-22 18:45:57
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> acdefghijklmnopqrstuvwxyz0123456789


When I hit the b key, I get a beep, and no character is echoed to the sqlite prompt.



If I try and see what tables I get using the .tables command, I get this:



sqlite> .tales
Error: unknown command or invalid arguments: "tales". Enter ".help" for help


So it's not merely failing to echo it, but rather the b just never gets entered at the prompt at all.



Why does this happen? I'm sure I'll kick myself when I find out!



I'm using the stock sqlite from Ubuntu 18.04:



$ dpkg -S $(which sqlite3)
sqlite3: /usr/bin/sqlite3
$ dpkg -s sqlite3 | grep ^Version
Version: 3.22.0-1






share|improve this question











If I fire up sqlite and then, at the prompt, type the letters a to z followed by the digits 0 to 9, I see this:



$ sqlite3 
SQLite version 3.22.0 2018-01-22 18:45:57
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> acdefghijklmnopqrstuvwxyz0123456789


When I hit the b key, I get a beep, and no character is echoed to the sqlite prompt.



If I try and see what tables I get using the .tables command, I get this:



sqlite> .tales
Error: unknown command or invalid arguments: "tales". Enter ".help" for help


So it's not merely failing to echo it, but rather the b just never gets entered at the prompt at all.



Why does this happen? I'm sure I'll kick myself when I find out!



I'm using the stock sqlite from Ubuntu 18.04:



$ dpkg -S $(which sqlite3)
sqlite3: /usr/bin/sqlite3
$ dpkg -s sqlite3 | grep ^Version
Version: 3.22.0-1








share|improve this question










share|improve this question




share|improve this question









asked Jul 28 at 21:50









Croad Langshan

1062




1062




closed as off-topic by Thomas Dickey, slm♦ Jul 29 at 4:15


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Thomas Dickey, slm
If this question can be reworded to fit the rules in the help center, please edit the question.




closed as off-topic by Thomas Dickey, slm♦ Jul 29 at 4:15


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Thomas Dickey, slm
If this question can be reworded to fit the rules in the help center, please edit the question.







  • 1




    Does ~/.inputrc exist?
    – Ignacio Vazquez-Abrams
    Jul 28 at 22:01










  • Yes! That was it! And I did mentally kick myself
    – Croad Langshan
    Jul 28 at 22:43










  • Not actually sure what's wrong with that file: $ cat ~/.inputrc bind \C-b:unix-filename-rubout
    – Croad Langshan
    Jul 28 at 22:45










  • This question has come up before, and seems to have been closed and then deleted, probably for the same reason as people want to close it now. This is a shame, because clearly it is a problem that can be reproduced, and has been by multiple people coming to StackExchange to report odd keys not working over the years.
    – JdeBP
    Jul 29 at 0:12










  • @JdeBP Probably a good candidate for a canonical duplicate target if you want to write one.
    – Michael Homer
    Jul 29 at 4:29












  • 1




    Does ~/.inputrc exist?
    – Ignacio Vazquez-Abrams
    Jul 28 at 22:01










  • Yes! That was it! And I did mentally kick myself
    – Croad Langshan
    Jul 28 at 22:43










  • Not actually sure what's wrong with that file: $ cat ~/.inputrc bind \C-b:unix-filename-rubout
    – Croad Langshan
    Jul 28 at 22:45










  • This question has come up before, and seems to have been closed and then deleted, probably for the same reason as people want to close it now. This is a shame, because clearly it is a problem that can be reproduced, and has been by multiple people coming to StackExchange to report odd keys not working over the years.
    – JdeBP
    Jul 29 at 0:12










  • @JdeBP Probably a good candidate for a canonical duplicate target if you want to write one.
    – Michael Homer
    Jul 29 at 4:29







1




1




Does ~/.inputrc exist?
– Ignacio Vazquez-Abrams
Jul 28 at 22:01




Does ~/.inputrc exist?
– Ignacio Vazquez-Abrams
Jul 28 at 22:01












Yes! That was it! And I did mentally kick myself
– Croad Langshan
Jul 28 at 22:43




Yes! That was it! And I did mentally kick myself
– Croad Langshan
Jul 28 at 22:43












Not actually sure what's wrong with that file: $ cat ~/.inputrc bind \C-b:unix-filename-rubout
– Croad Langshan
Jul 28 at 22:45




Not actually sure what's wrong with that file: $ cat ~/.inputrc bind \C-b:unix-filename-rubout
– Croad Langshan
Jul 28 at 22:45












This question has come up before, and seems to have been closed and then deleted, probably for the same reason as people want to close it now. This is a shame, because clearly it is a problem that can be reproduced, and has been by multiple people coming to StackExchange to report odd keys not working over the years.
– JdeBP
Jul 29 at 0:12




This question has come up before, and seems to have been closed and then deleted, probably for the same reason as people want to close it now. This is a shame, because clearly it is a problem that can be reproduced, and has been by multiple people coming to StackExchange to report odd keys not working over the years.
– JdeBP
Jul 29 at 0:12












@JdeBP Probably a good candidate for a canonical duplicate target if you want to write one.
– Michael Homer
Jul 29 at 4:29




@JdeBP Probably a good candidate for a canonical duplicate target if you want to write one.
– Michael Homer
Jul 29 at 4:29















active

oldest

votes






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?