mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-07 23:32:42 +01:00
Author:halw
Date:2009-11-11T05:07:08.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@353 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
Binary file not shown.
|
After Width: | Height: | Size: 8.8 KiB |
@@ -0,0 +1,3 @@
|
||||
title=Outputs tool Open folder
|
||||
author=halw
|
||||
path=content/outputs-tool-open-folder
|
||||
BIN
documentation/current/eiffelstudio/_images/terminal-icon.png
Normal file
BIN
documentation/current/eiffelstudio/_images/terminal-icon.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 737 B |
@@ -0,0 +1,3 @@
|
||||
title=terminal-icon
|
||||
author=halw
|
||||
path=content/terminal-icon
|
||||
@@ -15,9 +15,21 @@ The external compilation pane shows a log of the compilation output from the ext
|
||||
|
||||
==Selecting your locale==
|
||||
|
||||
If the external compiler uses a different locale than your default locale, you can select your particular locale in the "Locale" box.
|
||||
If the external compiler uses a different locale than your default locale, you can select your particular locale in the "Locale" box on the bottom bar of the Outputs tool.
|
||||
|
||||
==Open a file mentioned in the external compilation output==
|
||||
==Opening a project folder==
|
||||
|
||||
You can explore a project folder by using '''open folder''' ( [[Image:general-open-icon|open]] ) on the bottom bar. When you click the triangle ( [[Image:toolbar-dropdown-icon]] ) to the right of the '''open folder''' icon, you will see a list of project folders, as shown in the figure below.
|
||||
|
||||
[[Image:Outputs tool Open folder|open]]
|
||||
|
||||
Selecting one of this will cause the folder to be opened by the explorer appropriate to your platform, such as Windows Explorer in the case of the Microsoft Windows platform.
|
||||
|
||||
==Starting a terminal session in a project folder==
|
||||
|
||||
The Outputs tool gives you a way to create a new terminal or console window targeted to one of your project folders. To do this, click the triangle ( [[Image:toolbar-dropdown-icon]] ) to the right of the '''terminal''' icon ( [[Image:terminal-icon|terminal]] ). You'll see a list of project folders like the one shown [[#Opening a project folder|above]]. Choose a folder and a terminal window will be created and targeted to the folder you selected.
|
||||
|
||||
==Opening a file mentioned in the external compilation output==
|
||||
|
||||
You can open a file mentioned in the external compiler output in a specified external editor by selecting the file name and then clicking the '''send to external editor''' ( [[Image:metrics-tool--command-send-to-external-editor-icon|send to external editor]] ) button, shown in the bottom bar of the following figure:
|
||||
|
||||
|
||||
@@ -172,6 +172,12 @@ Another not-so-obvious CAP is related to the use of the logical implication:
|
||||
</code>
|
||||
|
||||
|
||||
==The bottom line on CAPs==
|
||||
|
||||
In summary, CAPs provide void-safe protection for certain types of detachable expressions.
|
||||
|
||||
Possibly the characteristic of CAPs which is most important to developers is whether or not a particular CAP is supported by the compiler. In other words, if the compiler can provide assurance that a certain code pattern provides void-safe protection, then the developer has that pattern available as a CAP. Likewise, even if a pattern can be shown to be a CAP, but for some reason it is not supported by the compiler, then that pattern is not available as a CAP and the compiler will not allow its use.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user