Here's one way to confirm all segments: Click segment 2, then shift-click segment 1, then press Ctrl-Enter.

This would not store your edits though. You have to run the Update TMs batch task. The same effect can be attained when you press Ctrl+Shift+A to select all segments and then change their status to Translated (confirmed but not stored)

Johnathan Barker 

It is always a good idea to use the Finalize batch at the end. This way you generate target and update the TM.

When you work with project TMs (as I always do), this is a simple necessity to have your final translations stored in your TM. IMO the habit in working with Studio should be:

• Open for translation, translate, save
• Open for revision, make your checks and changes
• Save copy of the sdlxliff file for tracking of the step done (must be done, if you are ISO certified, can be done for own tracking of work)
• Accept the changes done, change the status of changed segment to translated
• Close the file, confirm changing status of all segments
• Run finalize batch

Yeah, I see you often go like "I don't know why you may need that guys, for any reasons beyond my understanding, because I never do that. Do what I do..."
The workflow you described above is too long and complicated for a simple task like 'confirm all segments'. I should not be surprised if you create a project every time you get a translation assignment. However, I don't mind if you like it. It was just a kind reminder that you should remember to store segments.

Yeah, I see you often go like "I don't know why you may need that guys, for any reasons beyond my understanding, because I never do that. Do what I do..."
The workflow you described above is too long and complicated for a simple task like 'confirm all segments'. I should not be surprised if you create a project every time you get a translation assignment. However, I don't mind if you like it. It was just a kind reminder that you should remember to store segments.

I am working only with projects in Studio, as this is the easiest way to keep track of what is happening.

Beside this, opposite to what you state, creating projects is the fastest way to work with Studio in case you have many different settings depending on the customer or other options. It is just calling a template and adding files, setting up paths and that's it. I understand there may be different needs, but having a defined way of working with a tool is a good method to avoid errors.

This said, I assumed, updating the TM AFTER you create your final translation is a general habit.