Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "CDT/User/NewIn103"

< CDT
(Add dividing lines between entries.)
(Terminal: Bug 453696 and Bug 573645)
Line 144: Line 144:
 
* otherwise the user is prompted with the open resource dialog, pre-filled with the word
 
* otherwise the user is prompted with the open resource dialog, pre-filled with the word
  
See [https://eclip.se/563015 bug 563015].
+
See [https://eclip.se/563015 bug 563015]. Also see [https://eclip.se/573645 bug 573645] which is a helpwanted bug for how to detect current path on Windows and macOS.
  
 
[[File:Terminal-hover-selection.png]]
 
[[File:Terminal-hover-selection.png]]
Line 150: Line 150:
  
 
----
 
----
 +
----
 +
{| style="width: 100%;"
 +
|- style="vertical-align:top;"
 +
! style="width: 30%; text-align:left;" | Local terminals remember the path between restarts
 +
| When restarting the Eclipse IDE, the terminals will remember which path to start in. On Linux the path will be the detected path of the shell at shutdown, on Windows and macOS the path will be the initial path that shell was created with.
 +
See [https://eclip.se/453696 bug 453696]. Also see [https://eclip.se/573645 bug 573645] which is a helpwanted bug for how to detect current path on Windows and macOS.
 +
|}
 +
 +
----
 +
 
= Code Templates =
 
= Code Templates =
 
----
 
----

Revision as of 14:57, 19 May 2021


Release


This is the New & Noteworthy page for CDT 10.3 which is part of Eclipse 2021-06 Simultaneous Release


pack200 (*.jar.pack.gz) removed From CDT 10.3 pack.gz (aka pack200) jar files are not included with CDT release. (bug 572347).


Editor




Refactoring




Code Analysis




Parser




Formatter




Build


Headless builder can now remove projects from workspace. There are new two options based on the import options that will be executed before a build:

"-remove" /path/to/project - will remove a single project from workspace.
"-removeAll" /path/to/projectTree - will remove a tree of projects in this path.
Both options are more precedence than the import options. That means if you import a project and remove it or the containing project tree in the same command, the project will not be imported. Otherwise it is possible to combine the options with importing in this way:
-importAll /path/to/projectTree -remove<All> /path/to/projectTree/subProject<Tree>
This will import a project tree and remove the sub project or sub project tree.
See also Bug 573512.


Add verbose option for progress monitor of headless builder. During operations, such as remove projects, the subtask of a progress

monitor has useful information for users. However during a normal build there ends up being lots of output that is of little value.
See also Bug 573512.



Build command arguments moved to Behavior tab. The free form text box to customize build (aka make) arguments has been moved the the Behavior tab and split

from the Build command text box.
CDT 10 3 make args.png
See also Bug 568397.


Build Targets (Make) view supports working sets The Build Targets (Make) view now supports working sets allowing you to focus on what you are actively working on.

CDT 10 3 working sets.png
See also Bug 338776.


Build Targets (Make) view saves and restores its UI state The selected items, expanded folders and scroll positions of the Build Targets (Make) view are saved when closed and restored when reopened.

See also Bug 573619.


Debug


Show opcode as byte sequence The instruction opcode is shown as sequence of bytes inside the disassembly view.

See bug 572880.

Opcode as byte sequence.png


Jump To Memory location context menu The disassembly view got a new context menu entry to jump to memory location for the current selected entry.

See bug 573157.

Jump to memory.png


Launch Bar




Terminal


Open files and links with Ctrl+Click When pressing the Ctrl key (Cmd key on mac), the word under the mouse pointer is highlighted with an underline and by clicking it the terminal guesses how to open it:
  • a web link is opened in the configured browser
  • if it can be resolved to a file in the workspace, that file is opened (linux only: the terminal keeps track of the current working directory of the shell to resolve relative paths)
  • otherwise the user is prompted with the open resource dialog, pre-filled with the word

See bug 563015. Also see bug 573645 which is a helpwanted bug for how to detect current path on Windows and macOS.

Terminal-hover-selection.png



Local terminals remember the path between restarts When restarting the Eclipse IDE, the terminals will remember which path to start in. On Linux the path will be the detected path of the shell at shutdown, on Windows and macOS the path will be the initial path that shell was created with.

See bug 453696. Also see bug 573645 which is a helpwanted bug for how to detect current path on Windows and macOS.


Code Templates


Templates are sorted

When a new source file is created from template, the available suggested templates are sorted in alphabetical order first by template key, then by template name between same content type. E.g. When a new C++ file is created from template it will have few suggested templates grouped into few content types. The most relevant content type group is still at the top. It makes possible to bring at the top of the drop down list custom templates that does not have a key and whose name sorted will be in front of "Default C++ Source template". See Bug 572755


Templates selection is persistent

The template selection is persistent. If a different template has been selected than default one from the top of the list, this selection will be recorded. Next time when a new file is created from template with same extension, the previous chosen template will selected by default. See Bug 573204


API modifications


org.eclipse.cdt.dsf.gdb

A new method org.eclipse.cdt.dsf.gdb.service.IGDBBackend.getDebuggerCommandLineArray() has been added for access to, and customization of, the GDB command line used when launching a debug session. This method should be overridden by extenders in preference to overriding org.eclipse.cdt.dsf.gdb.service.GDBBackend.getDebuggerCommandLine() or org.eclipse.cdt.dsf.gdb.service.GDBBackend.getGDBCommandLineArray() which are now deprecated. See Bug 572944


Bugs Fixed in this Release


See Bugzilla report Bugs Fixed in CDT 10.3


Back to the top