1

There are two tags:

and

Neither have tag wikis and frankly I don't know which of them to use. Is there a difference?

6
  • In your case, command line. – user3 Jul 12 '15 at 9:45
  • How do you differentiate between their uses? – Huey Jul 12 '15 at 9:46
  • Command line is about running commands. Terminal is about the application itself. – user3 Jul 12 '15 at 9:47
  • So only questions specific to the default terminal emulator should be tagged with terminal? – Huey Jul 12 '15 at 9:48
  • Anything about it, yes. e.g. settings, colours etc – user3 Jul 12 '15 at 9:50
  • Got it. If you post that as an answer I'll accept it. – Huey Jul 12 '15 at 9:51
4

is for the actual GUI program, pantheon-terminal. Use this tag when configuring it, like changing the transparency, text colour or font etc.


Command line is for running commands - this could be using any terminal - tty, gnome-terminal or pantheon-terminal. Whichever it is, if this tag is used, the terminal being used shouldn't matter. Anything tagged should apply to any bash terminal.

3
3

Yes, there is a difference between “command line” and “terminal”. The most relevant difference, in fact, is between shell and terminal. The shell is the program that interprets commands. It's also the program that displays a prompt and provides facilities to edit commands when you type it. Bash is the default shell; there are others. The terminal (more precisely a terminal emulator) is the program that provides basic character input/output. Pantheon Terminal is the default terminal emulator programs; there are others.

What does this mean in terms of tags? Given that the command line is not the primary focus of this site, I think it would make sense to have a tag that covers all command line issues, whether they're with bash or with the terminal (most issues are with the shell anyway).

There shouldn't be a tag , but there should be a tag for issues about Pantheon Terminal specific features such as using tabs, saving sessions, configuring colors, etc.

There shouldn't be a tag , but there should be a tag for bash-specific issues such as prompt settings, command history, command line editing, etc. There should also be a tag for when the shell is used to run scripts rather than interactively.

I expect questions to be asked mostly with the tag, and tags such as and to be added where relevant.

This isn't the tags we use on Unix & Linux — there we strictly distinguish between generic shell use ([shell]), features of specific shells ([bash], etc.), terminal issues ([terminal]), features of specific terminal emulators ([xterm], etc.), and we have a tag [command-line] that we don't quite know what to do with. But U&L has a very different audience — primarily command-line-based — so different tags are warranted.

You must log in to answer this question.

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