Hi @kennyk65, aws-shell has dot commands so running either of the following commands will terminate the shell:

aws> .quit
aws> .exit

In the README we make note of .cd and .profile but not .quit/.exit.

I think we could probably make these commands more discoverable.

I would never guess to try ".exit" or ".quit". Why force customers to look in the documentation when they only wish to leave the tool?

@donnemartin or maybe just do like EVERYONE is doing, provide a quit and/or exit methods. Seriously!!

I can definitely understand the frustration behind not being able to exit the shell. The problem with allowing arbitrary commands is the potential for naming collisions with services under the aws command. The idea is that the commands you type are under the prefix aws and thus just exit would equate to aws exit. If we make a special exception for some commands and not others may only further confusion. That being said, such a fundamental command may be worthy of the exception. @jamesls Any thoughts on this?

Yeah, I'm interested in a better solution here, but I think we should at least start with documenting .quit and .exit. While it seems highly unlikely there will ever be an exit or quit command in the AWS CLI (i.e aws exit), it does make things inconsistent with the way that namespace is used for other services (e.g aws ec2 ...).

Checking out a few existing REPLs: python, node don't have quit/exit commands, but irb and ipython do. It seems like it's not entirely consistent to always add quit/exit commands.

I'd say, let's leave this issue open. If people feel strongly about this, please +1 this issue. That will help give us feedback if people want this or are fine with the .quit/.exit commands. I think that's probably the best way to decide.

Alternatively, some guidance on how to discover the dot commands when first starting up would be good - ipython for instance tells you "press ?" to know more. The design of the .exit / .quit makes sense, but are not easily discoverable.

On the other hand, it didn't me long to discover ^D, after quit and exit didn't work, it was the next obvious go-to, though this might be less obvious to Windows users (and in which case it would likely be ^Z)

It does seem annoying that "exit" doesn't work however, personally I'd prefer to see that additionally supported, alternatively - describing the presence of the .dot commands and how to bring up a quickref for them (e.g. "?") would be a workable alternative.

I've been using AWS Shell for several weeks now, mostly because I can't figure out how to exit it.

Ironically, the only place I could find info about how to quit the terminal is... this Github issue!

+1

What about support for Ctrl+C? That's the first thing I tried...

I would never guess to try ".exit" or ".quit". Why force customers to look in the documentation when they only wish to leave the tool?

Because I have to install "Cheese" in order to use my webcam with Ubuntu. Sounds pretty obvious to me eh !

I've just installed it on mac and I've noticed when I started, it creates a bar on the bottom:

[F2] Fuzzy: ON  [F3] Keys: Emacs  ...  [F10] Exit 

hence, pressing F10 (or fn + F10 on new macs) also exit the shell.

I've just installed it on mac and I've noticed when I started, it creates a bar on the bottom:

[F2] Fuzzy: ON  [F3] Keys: Emacs  ...  [F10] Exit 

hence, pressing F10 (or fn + F10 on new macs) also exit the shell.

Interestingly this doesn't work for Linux but i found .q helped out.

Why did the F10 not work on "Linux"? Is it captured by the terminal emulator? Try Esc 0 or try running aws-shell from the TTY?

F10 on ubuntu opens the top menu bar of the terminal. I just installed the package and the interesting thing is that this issue is still opened for almost 3 years now and l landed here just to help myself exit. How hard is it to make Ctrl+C for exit and make Ctrl+D for keyboard interrupt? It should be 2 line edit on code and docs.