mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2026-02-10 04:24:18 +01:00
Author:halw
Date:2009-11-13T16:43:03.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@356 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
@@ -8,10 +8,12 @@
|
||||
|
||||
By configuring external commands, you can set up EiffelStudio to execute basic commands for Subversion or other source code management (SCM) systems. Source code management systems, sometimes called revision control or version control systems are often used as part of a software configuration management strategy to track and control changes to software and its supporting documents.
|
||||
|
||||
|
||||
==Defining external commands==
|
||||
|
||||
You can define external commands by using the [[External commands editor dialog|external commands editor dialog]]. Then you can execute those commands through the '''Tools''' menu or with keyboard shortcuts.
|
||||
|
||||
|
||||
===Defining a Subversion command===
|
||||
|
||||
Suppose that you want to add an external command to EiffelStudio to Subversion's ''update'' command (''update'' brings your working copy up-to-date with the repository). You can define a command with an appropriate name, say ''svn update'', as shown below.
|
||||
@@ -28,6 +30,12 @@ Once the command is defined, it will be accessible through EiffelStudio's Tools
|
||||
[[Image:subversion-update-in-tools-menu|Subversion update command in the tools menu]]
|
||||
|
||||
|
||||
You can uses this same technique to add external commands for other Subversion commands that require only a basic form. For example, to create a command that will add the file for the currently edited class to the repository, add a new external command with the command line:
|
||||
<code lang="text">
|
||||
svn add $file_name
|
||||
</code>
|
||||
|
||||
|
||||
===The option to confirm execution of a command===
|
||||
|
||||
Now imagine that you want your command to Subversion to offer you a chance to back out of the deal before it executes. You can do this by adding a little more to the command line:
|
||||
@@ -38,7 +46,13 @@ Now imagine that you want your command to Subversion to offer you a chance to ba
|
||||
|
||||
Here the command line first asks for confirmation before executing the command.
|
||||
|
||||
When you execute this command you will see the confirmation prompt in EiffelStudio's [[Console tool|Console tool]]. If you choose to execute the command, then just press <code>return</code>. If you have second thoughts and want to cancel the command, then do so by clicking the Console tool's stop button ( [[Image:metrics-tool--debug-stop-icon|Stop command]] ).
|
||||
When you execute this command you will see the confirmation prompt in EiffelStudio's [[Console tool|Console tool]]:
|
||||
|
||||
|
||||
[[Image:subversion-update-console-tool|Subversion update command with confirmation]]
|
||||
|
||||
|
||||
If you choose to execute the command, then just press <code>return</code>. If you have second thoughts and want to cancel the command, then do so by clicking the Console tool's stop button ( [[Image:metrics-tool--debug-stop-icon|Stop command]] ).
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ The [[Breakpoint editing|breakpoint menu]] lets you change the state of one bre
|
||||
{{note|You can toggle the status of a breakpoint easily using shortcuts<br/> - '''F9''': toggle between enabled/not-set. <br/> - '''Shift+F9''': toggle between enabled/disabled.<br/> - '''Ctrl+F9''': open the breakpoint dialog for [[Breakpoint editing|editing]]. }}
|
||||
|
||||
{{note|Breakpoints cannot be set in all features. In particular, breakpoints cannot be set in external features or attributes. <br/>
|
||||
However, breakpoints can now be set in assertions (require and ensure). }}
|
||||
However, breakpoints can be set in assertions (require and ensure). }}
|
||||
|
||||
{{tip|Breakpoints can be set on-the-fly while the application is running. }}
|
||||
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
[[Property:title|Execution profiles]]
|
||||
[[Property:weight|-13]]
|
||||
[[Property:uuid|90e64e1c-b5fc-e150-9901-50daffaac893]]
|
||||
While working on a project, you may want to launch your system with one or more arguments, on specific working directory, and you may want to change the environment variables.
|
||||
While working on a project, you may want to launch your system with values for one or more arguments, specify a working directory, and/or change certain environment variables.
|
||||
|
||||
Those parameters are done by changing the execution profiles. For that you need to use the '''Execution parameters''' dialog.
|
||||
|
||||
* Open this dialog either:
|
||||
** From the EiffelStudio menu path: <code>Execution -> Execution parameters</code> .
|
||||
** By right-clicking any of the buttons on the debugging/execution toolbar.
|
||||
* You can open this dialog in either of two ways:
|
||||
** Follow the EiffelStudio menu path: <code>Execution -> Execution parameters</code> .
|
||||
** Right-click any of the buttons on the debugging/execution toolbar.
|
||||
|
||||
==Using the Execution parameters' dialog==
|
||||
|
||||
@@ -18,14 +18,15 @@ The dialog allows you to manage different execution profiles to specify paramete
|
||||
|
||||
Each profile lets you set a title, the '''arguments''', the '''working directory''', as well as your own '''environment variables'''.
|
||||
|
||||
To use a profile, just select it by clicking the corresponding line in the grid..
|
||||
To use a profile, just select it by clicking the corresponding line in the grid.
|
||||
|
||||
Once the appropriate execution profile is selected then the system can be run with those parameters using the Run button (If "Keep Dialog Open" is selected the dialog remains opened).<br/>
|
||||
To run without any particular parameter select the '''default''' profile.
|
||||
To run without any particular parameters, select the '''default''' profile.
|
||||
|
||||
If you click on "Run Workbench" or "Run Finalized", the system will be executed outside EiffelStudio (thus debugging is unavailable)..
|
||||
If you click on "Run Workbench" or "Run Finalized", the system will be executed outside EiffelStudio (thus debugging is unavailable).
|
||||
|
||||
{{tip|From version 6.5, you can unset an environment variable FOO by adding the "&-FOO" to the environment variables, by prefixing with "&-", this marks the variable "FOO" to be removed. If you use "&-*", all variables will be removed (except the one you can still add after this "&-*"). }}
|
||||
|
||||
{{tip|From version 6.5, you can unset an environment variable FOO by adding the "&-FOO" to the environment variables. By prefixing with "&-", you mark the variable "FOO" to be removed. If you use "&-*", all variables will be removed (except for any that you add to the list after the "&-*" entry). }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
[[Property:title|Run with arguments]]
|
||||
[[Property:weight|-14]]
|
||||
[[Property:uuid|0c8c089c-f953-3337-87dc-09a0c8150c21]]
|
||||
While working on a project, you may want to launch it with one or more arguments.
|
||||
While working on a project, you may want to launch your system with one or more arguments.
|
||||
|
||||
There are two ways to specify arguments for a program from EiffelStudio:
|
||||
* From the '''Execution, Execution parameters''' menu.
|
||||
There are two ways to access the '''Execution Parameters''' dialog which lets you specify arguments to be used by your system when launched from EiffelStudio:
|
||||
* By following the EiffelStudio menu path: <code lang="text">Execution -> Execution parameters</code> .
|
||||
* By right-clicking any of the buttons on the debugging toolbar.
|
||||
|
||||
See the [[Execution profiles|Execution parameters dialog]] for more details.
|
||||
|
||||
Reference in New Issue
Block a user