Translations:KDevelop5/Manual/Working with source code/17/en: Difference between revisions

Revision as of 00:48, 22 March 2020

Information about message (contribute)

This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.

Message definition (KDevelop5/Manual/Working with source code)

If you open '''KDevelop''' the first time, the working set is empty — there are no open files. But as you open files for editing (or debugging, or reviewing in the other modes) your working set grows. You will notice that whenever you close '''KDevelop''' and later start it again, the working set is saved and restored, i.e. you get the same set of open files.

If you open KDevelop the first time, the working set is empty — there are no open files. But as you open files for editing (or debugging, or reviewing in the other modes) your working set grows. The fact that your working set is non-empty is indicated by a symbol in the tab, as shown below. You will notice that whenever you close KDevelop and later start it again, the working set is saved and restored, i.e. you get the same set of open files.

Revision as of 00:48, 22 March 2020 view source FuzzyBot (talk \| contribs) 50,556 edits Importing a new version from external source		Revision as of 00:48, 22 March 2020 view source FuzzyBot (talk \| contribs) 50,556 edits Importing a new version from external source Newer edit →
Line 1:		Line 1:
	If you open '''KDevelop''' the first time, the working set is empty — there are no open files. But as you open files for editing (or debugging, or reviewing in the other modes) your working set grows. You will notice that whenever you close '''KDevelop''' and later start it again, the working set is saved and restored, i.e. you get the same set of open files.		If you open '''KDevelop''' the first time, the working set is empty — there are no open files. But as you open files for editing (or debugging, or reviewing in the other modes) your working set grows. The fact that your working set is non-empty is indicated by a symbol in the tab, as shown below. You will notice that whenever you close '''KDevelop''' and later start it again, the working set is saved and restored, i.e. you get the same set of open files.