Please add open Properties of View, Find Modified Files and Update View.
These would be nice commands to have. I don't use them as often as the commands that are already implemented. Thanks.

Is it possible to prevent the error message ("Failed to save 'file': File is write protected ...") by checking out before the save starts. Also, it possible to use a dialog box that is internal to Visual Studio Code, rather than launching the ClearCase dialog box, and use the ClearCase command tools to do the check out.

The "Toggle Annotation" code lens activates even when the opened file is not a clearcase object.
This is strange because I was under the impression that the whole extension was not activated if the workspace is not a clearcase vob.

We have written the needed data into your clipboard because it was too large to send. Please paste.

I added support for the cleartool annotate command ( in some situations it's a godsent ) but the UI is terrible ( it just open a text document with the output of the cleartool command ).

We need a better way to display those informations ( for example https://github.com/eamodio/vscode-gitlens does a great work! )

Hi there,

While searching for a solution I found this issue:
microsoft/vscode#25402
There it is mentioned, that the scrolling while typing bug happens only with Code-Lense on. Therefore I disabled all Code-Lense features from every extension I had separately and the clearcase extension was the evil guy.

It is reproducible on several PCs with C-Code. I turned Code-Lense on for everything except clearcase then it works as intended. When turning on "vscode-clearcase.showAnnotationCodeLens" it is scrolling down while typing text.

The extension should detect hijacked files on snapshot views as well as file in checkout state and mark with a symbol (e.g. H) in the SCM tab.
We could also add related commands ( only for snapshot views ):

• Hijack File
• Undo Hijack File

Hi,
Thanks for working on this extension, it's nice to have at least some level of integration between vscode and clearcase.

Below are the contents of the "Clearcase SCM" output channel when opening my project.
My environment is a bit special, but the observed issue is probably a generic one:

• using Clearcase dynamic views on a remote server (Windows local machine, Linux remote, although probably irrelevant);
• using "Remote SSH" to connect to the server with the Clearcase view(s);
• not executing in a shell created by ct setview taskname, but accessing the files over Clearcase MVFS (in /view/<taskname>);
• my.code-workspace is outside clearcase (not a view-private file, but really outside the VOB(s)), so the error messages are correct, only weirdly truncated;

The problem seems to be with onError in runCleartoolCommand, which fires on random chunks of data (in my case it seems to process one letter at a time at first, then the last part - truncated more or less randomly - in one go). This generates the output pasted below + some error messages that usually have a truncated error message (the last chunk of stderr).

As far as I can tell, it doesn't really break anything, it's just ugly and annoying.

Also, looking at the callers of runCleartoolCommand, it seems that onError is treated like a one-time event and not a stream of events for each chunk of data. Since stderr is rarely getting huge blocks of data, it would make sense to treat the handling of stderr contents during the "close" event, similar to onFinished. In fact, combining onFinished with onError would make the code easier to follow in my opinion, but that's up to you.

I will submit a PR as a proof of concept for the change. Since I don't have a standard environment, nor do I use all the features in the extension, I can't test most of the things changed (e.g. login).

catcs
lsview,-cview,-long
lsco,-me,-cview,-short,-avobs
ls,-d,-short,/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace
ls,-d,-short,/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace
ls,-d,-short,/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace
clearcase, exec error: c
clearcase, exec error: l
clearcase, exec error: e
clearcase, exec error: a
clearcase, exec error: r
clearcase, exec error: t
clearcase, exec error: o
clearcase, exec error: o
clearcase, exec error: l
clearcase, exec error: :
clearcase, exec error:  
clearcase, exec error: E
clearcase, exec error: r
clearcase, exec error: r
clearcase, exec error: o
clearcase, exec error: r
clearcase, exec error: :
clearcase, exec error:  
clearcase, exec error: P
clearcase, exec error: a
clearcase, exec error: t
clearcase, exec error: h
clearcase, exec error: n
clearcase, exec error: a
clearcase, exec error: m
clearcase, exec error: e
clearcase, exec error:  
clearcase, exec error: i
clearcase, exec error: s
clearcase, exec error:  
clearcase, exec error: n
clearcase, exec error: o
clearcase, exec error: t
clearcase, exec error:  
clearcase, exec error: w
clearcase, exec error: i
clearcase, exec error: t
clearcase, exec error: h
clearcase, exec error: i
clearcase, exec error: n
clearcase, exec error:  
clearcase, exec error: a
clearcase, exec error:  
clearcase, exec error: V
clearcase, exec error: O
clearcase, exec error: B
clearcase, exec error: :
clearcase, exec error:  
clearcase, exec error: "
clearcase, exec error: /

[ ... redacted ... basically each letter of the redacted path ...]

clearcase, exec error: .
clearcase, exec error: c
clearcase, exec error: o
clearcase, exec error: d
clearcase, exec error: e
clearcase, exec error: -
clearcase, exec error: w
clearcase, exec error: o
clearcase, exec error: r
clearcase, exec error: k
clearcase, exec error: s
clearcase, exec error: p
clearcase, exec error: a
clearcase, exec error: c
clearcase, exec error: e
clearcase, exec error: "
clearcase, exec error: 


catcs
clearcase, exec error: cleartool: Error: Pathname is not within a VOB: "/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace"


catcs
clearcase, exec error: cleartool: Error: Pathname is not within a VOB: "/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace"


catcs
lsview,-cview,-long
ls,-d,-short,/view/taskname/vobs/full/pathname/redacted/sourcefile
ls,-d,-short,/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace
clearcase, exec error: cleartool: Error: Pathname is not within a VOB: "/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace"


catcs
ls,-d,-short,/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace
clearcase, exec error: cleartool: Error: Pathname is not within a VOB: "/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace"


catcs
ls,-d,-short,/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace
clearcase, exec error: cleartool: Error: Pathname is not within a VOB: "/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace"


catcs
ls,-d,-short,/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace
ls,-d,-short,/view/taskname/vobs/full/pathname/redacted/sourcefile
ls,-d,-short,/view/taskname/vobs/full/pathname/redacted/sourcefile
clearcase, exec error: cleartool: Error: Pathname is not within a VOB: "/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace"


ls,-d,-short,/view/taskname/vobs/full/pathname/redacted/sourcefile
ls,-d,-short,/view/taskname/vobs/full/pathname/redacted/sourcefile
ls,-d,-short,/full/pathname/redacted/but/ouside/clearcase/vobs/my.code-workspace
ls,-d,-short,/view/taskname/vobs/full/pathname/redacted/sourcefile
ls,-d,-short,/view/taskname/vobs/full/pathname/redacted/sourcefile
clearcase, exec error: c
clearcase, exec error: l
clearcase, exec error: e
clearcase, exec error: a
clearcase, exec error: r
clearcase, exec error: t
clearcase, exec error: o
clearcase, exec error: o
clearcase, exec error: l
clearcase, exec error: :
clearcase, exec error:  
clearcase, exec error: E
clearcase, exec error: r
clearcase, exec error: r
clearcase, exec error: o
clearcase, exec error: r
clearcase, exec error: :
clearcase, exec error:  
clearcase, exec error: P
clearcase, exec error: a
clearcase, exec error: t
clearcase, exec error: h
clearcase, exec error: n
clearcase, exec error: a
clearcase, exec error: m
clearcase, exec error: e
clearcase, exec error:  
clearcase, exec error: i
clearcase, exec error: s
clearcase, exec error:  
clearcase, exec error: n
clearcase, exec error: o
clearcase, exec error: t
clearcase, exec error:  
clearcase, exec error: w
clearcase, exec error: i
clearcase, exec error: t
clearcase, exec error: h
clearcase, exec error: i
clearcase, exec error: n
clearcase, exec error:  
clearcase, exec error: a
clearcase, exec error:  
clearcase, exec error: V
clearcase, exec error: O
clearcase, exec error: B
clearcase, exec error: :
clearcase, exec error:  
clearcase, exec error: "
clearcase, exec error: /

[ ... redacted ... basically letters of the redacted path, one by one (up to a point, then the truncated remaining path chunk) ...]

clearcase, exec error: earcase/vobs/my.code-workspace"


ls,-d,-short,/view/taskname/vobs/full/pathname/redacted/sourcefile
ls,-d,-short,/view/taskname/vobs/full/pathname/redacted/sourcefile

I'm thinking about adding some commands to the statusbar version information.
This can simply be accomplished by assigning a command to the statusbar item, like

this.m_statusbar.command = "extension.ccStatusbarCmd"

When someone clicks the button, a quick pick list can be shown.
There such things as open in clearcase explorer or compare to previous version etc. can be listed.

What do you think about it?

Ctrl-Shift-P followed by "ClearCase: Find checkouts" stopped working. Error message "command 'extension.ccFindCheckouts' not found" is displayed. On the previous version of the extension, it worked.

Hello,

I forked your repo and added support for config-spec syntax.
If you are interested please have a look at

https://github.com/jsinger67/vscode-clearcase

If someone uses vscode as 'EDITOR' than 'ct edcs' will use vscode and this one can take advantage of the syntax highlighting of vscode.
I also accociated extension *.ics with this syntax.

This is perhaps not the most important feature but it is little invasive.

Feel free to close.
Jörg

Could you add launching of "Find Checkouts" for the current file's view. Or this could assume that that the open folder is the view root if this is required to launch "Find Checkouts".

Using the non dialog mode there is a bug:

If an error occurs on save & checkout the file cannot be saved.
So the error message saying file not writeable appears repeatedly and it is very annoying to get rid of it.

I will investigate this behavior.

I use a workspace that is using CC. When opening a file that is not located within my project (e.g. a system header or config file), the plugin tries to get CC infos about the file, which causes infinitely re-occuring notifications saying 'cleartool error: pathname is not within a VOB'.
Maybe the plugin could handle this particular cc error in a different way or make sure that the notification is displayed only once per file/pathname?

Make use of the multi select functionality within the tree view object.
Execute a clearcase command on every single selected tree view item.

when using this extension, many error messages shows like this
Cleartool error: Cleartool command lsco,-me,-cview,-short,-avobs exited with error code: 3221225781

the cleartool works correctly in a plain command line window

Using prettier (esbenp.prettier-vscode) for consistent code formatting.

Any checkouts that are made externally or before the editor was opened or before a reload window are not shown. Using the refresh checkouts button doesn't help. It used to work and pick up existing checkouts and those made during the editor session.

Name: Unofficial ClearCase SCM Commands
Id: openningia.vscode-clearcase
Description: Unofficial support for IBM Rational ClearCase most common commands
Version: 2.4.3
Publisher: OpenNingia
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=OpenNingia.vscode-clearcase

Version: 1.34.0 (user setup)
Commit: a622c65b2c713c890fcf4fbf07cf34049d5fe758
Date: 2019-05-15T21:59:37.030Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17134

If a checkout is undone in the console the user is asked:

Save private copy of "util.c"? [yes]

This behaviour is overwritten with the -rm option in

If -keep or -rm is used should be configurable or the preference for using cleardlg shall be used like in the checkin command

I'm thinking about adding a statusbar feature.
There could be the version information of the current file displayed in the statusbar.

The style could be something like: [/branch1/branch2/LATEST]

I think this should be easy to accomplish with an

cleartool ls ${file} -short.

What do you think?

I'm using Web-Views (ClearCase UCM) but unfortunately vscode-clearcase doesn't detect the files within this views as clearcase files.
Is there a way to support this kind of view?

Edit:
You can use the command rcleartool instead cleartool, see this link.
The available commands are listed here.
The presence of the .copyarea.db file could be used as indication, if you are in a web view.

Maybe we can add a configuration date to let the user decide what command should be executed if he clicks on a checked out file.
And by that also add an entry in the scm/resource/context depending what the user configured. Either open resource or show the diff

Build in a more specific when clause in the explorer/context area to only show the checkout item if the file is not checked out.
This operator will be supported in the upcoming version of vscode.

The extension has grown in size and now vsce ( the publishing tool ) warns about potential performance issues caused by the sheer amount of files.

> tsc -p ./

This extension consists of 244 separate files. For performance reasons, you should bundle your extension: https://aka.ms/vscode-bundle-extension

Microsoft released a guide to help us packaging the extension with Webpack:
https://code.visualstudio.com/api/working-with-extensions/bundling-extension

Visual Studio code introduced a way to integrate SCM other than GIT, we should investigate if it is possible to integrate Clearcase with these new API, however:

1. Official documentation is still missing
2. The way Clearcase operate is pretty unique ( files being read-only before the checkout is something I never saw in other SCM )
3. Is this integration actually more productive than the one we already have?

References:
microsoft/vscode#15894
microsoft/vscode#15246

vscode-clearcase.showVersionInStatusbar false doesn't disable the version info in status bar. I think it used to work. I disable this information as it uses a lot of space in the status bar.

When having a list of checked out and untracked files in the scm view and checking in one file breaks the list. After the checkin the untracked list is also shown as checkedout list.
After manually refreshing the list, it is ok again.

I will investigate this behavior.

My project is useing Clear Case Remote Client. It's a pretty old version. I wanna know dose the extension support it?

If a undo checkout is done via the scm panel inline command, the list of checkedout files is not refreshed.

I'm using ClearCase Remote Client to connect server to use.
I enter a url to connect clear case server, then use clear case.

And I printed my system path, but found nothing except a lot of "IBM\Rational\Shared\SA***.dll" 😢
How can I find A valid ClearCase installation?

Thanks! 😄

My organisation requires that we provide a checkout comment - we would like the ability to specify a default check out comment in the settings, and this to then be shown in the check out dialog box. From the command line it's just the -c option, so hopefully something similar is possible via the UI.

From issue #36.
The "VIEW PRIVATE" list in the "SOURCE CONTROL" tab is showing a lot of files that should be ignored. For example, I can see the .vscode directory, many ".obj, .exe, .bak" files and many.
I've noticed there is a "View Private File Suffixes" (defaulting to "(hh|cpp|def|c|h|txt)$"). However, is still showing a lot of other files (e.g. .obj, .exe, .bak, .vscode directory). I'm not sure how

If something is wrong with the workspace folder setup and the given path doesn't exist, then the spawn command shows an error message ENOENT (no such file or directory).
To avoid this behavior it would be useful to check the path before calling the command.

Found in

ClearCase.runCleartoolCommand()

This is an FYI message - fell free to close....

Hello,

Thanks for creating and extension for VS Code, we have now added an API for VSCode to enable pluggable SCM Providers. This is currently in the 'preview' state and only in the 'insiders' build. Our plan is to move this into 'stable' in our next release (early April 17).

This lays the foundation for rich SCM Extensions to be distributed through the marketplace. These extensions will have access to all of the features our Git support leverages (this itself is now only using the public API).

Our ASK If you are interested in helping create an SCM provider, we want to help you and have created a new repo with all of the required details including - timelines, instructions, sample implementations, ... https://github.com/Microsoft/vscode-SCMBuilders

Head on over there if you want to help to get going or to monitor progress - with any luck in the coming months we should have a set of high quality SCM providers for VS Code.

Sean
VS Code Team Member

Could it be that 'compare to previous version' utilises vs diff rather than clearcase diffmerge?

Hi,

I want to open the discussion about the new maintainer of this project.
@OpenNingia said, he has not enough time to keep on working on it. So I think a successor is needed.
At work I still use CC, so it is also in my interest to keep this extension up to date.

The view private list needs requires some minor fixes:

• add a view private file to that list if it gets opened and not already listed
• the internal handling of the list requires some work

While the extension shows checkedout files etc. correctly in the SCM view, the commands from the command palette do not work. Neither do the commands from the context menu.

Example:
I have a folder with two files, one checked in, the other checked out:

(.env) 20 testcases/abc 1 % ct ls            
CMakeLists.txt@@/main/1                                  Rule: /main/LATEST
notmain.cpp@@/main/CHECKEDOUT from /main/3               Rule: CHECKEDOUT

I now open notmain.cpp, right click the text and select "Undo Checkout". Looking at the folder listing I can see that it is unchanged and notmain.cpp is still checked out.
While doing that the extension logs

clearcase, stdout: /var/vob/cli_n28/ric/vob/verification/testcases/reset_generation/notmain.cpp@@/main/CHECKEDOUT from /main/3              Rule: CHECKEDOUT

catcs

to the output window.

Alternatively if I try to check out CMakeLists.txt I see similar behavior: the status of the file does not change and

clearcase, stdout: /var/vob/cli_n28/ric/vob/verification/testcases/reset_generation/CMakeLists.txt@@/main/1                 Rule: /main/LATEST

catcs

is added to the log output. Nothing else happens (like e.g. a comment entry box which I'd have expected from skimming the sourcecode)

Is there any way to make the logging more verbose to see what is going on?

Environment Information:

• RHEL 7
• vscode-clearcase.useClearDlg=false (since we do not have cleardlg)
• Extension: v2.7.0
• VSCode 1.60.2

When using the non dialog cleartool command the checkin command does not automatically create a versioned element of a view private element.
There are two new options:

• create a new command the user can call to start the mkelem command
• if configured, automatically create a versioned element if necessary.

What do you think?

Hi there; the "Toggle Annotations" tab keeps appearing for this embedded ClearCase error - it keeps disappearing and reappearing making my code jump every few lines I write. Has anyone seen thie "use no checkouts option" error?

Hi,

The extension pops-up an error notification for any file that is not in ClearCase.

cleartool: Error: Cannot get view info for current view: not a ClearCase object

I often use VS Code to open files that are not meant to be in ClearCase or I use other source control applications.

Wouldn't it be best to detect whether the file in question is in a VOB prior to the execution of cleartool?

If that's problematic then maybe a setting that will define the paths for which the cleartool execution is allowed. Prevents redundant process executions and avoid the notifications.

Extension version: v4.1.0
VS Code version: 1.69.2 (Commit: 3b889b090b5ad5793f524b5d1d39fda662b96a2a, Date: 2022-07-18T16:12:52.460Z)
OS version: Windows_NT x64 10.0.19041

Say I have the path series\implementation on the vob dev. ClearCase is configured to connect every view to a network location, e.g. X.
In my daily VS Code use I open the folder X:\dev\series\implementation as a workspace. The ClearCase extension detects everything and the context commands for checkin/checkout/versiontree etc with an open editor work perfect.
But in the SourceControl panel the list of checked out & view private files won't work, as the paths shown in slight grey behind the filename are not complete.

Example 1:

Checked out file is: X:\dev\series\implementation\folder1\file1.cpp
The List says:
file1.cpp folder1

Example 2:

Checked out file is: X:\dev\wip\dummy\folder1\file2.hpp
The List says:
file2.hpp \dev\wip\dummy\folder1

Due to this behaviour the extension / the cleartool can't resolve the filepath and won't do anything within this list except Checkin all.

Rightclick -> Version Tree on one element in the list gives the following message in the output:

clearcase, exec error: Error: Command failed: cleartool ls "\dev\wip\dummy\folder1\file2.hpp"
cleartool: Error: Unable to access "\dev\wip\dummy\folder1\file2.hpp": No such file or directory.

I use latest VS Code on Windows 10 and also update all extensions regularly.

Instead of showing version information in the status bar, how about showing it in the hover over on the file name at the top of the tab. VS Code shows the full path filename at the moment. Would it be possible to add the version information below the filename? This would provide the information without occupying valuable space on the status bar.

This extension isn't working for me on Linux.

Diff, undo checkout and version tree work
Annotation works
Checkin / Checkout do not work, they don't do anything

Since the latest update from yesterday (v3.0.1) the extension constantly produces error messages of the kind "Unable to access ..." as in the following screenshot:

These errors appear every time a new unsaved file gets created via File > New Text File (Ctrl+N) or a tab with such an unsaved file gets activated. The same happens when clicking into the "Output" panel (upper error in the screenshot), probably vscode internally handles it as some kind of "file" as well.

If you work a lot with unsaved files like me, e.g. to temporarily paste some text, then this gets annoying quickly.

From a quick look I think this behavior was introduced by commit 426fef7 from the changes made to clearbase.ts from line 803. I would really appreciate if you could fix this.

Otherwise, thank you for this very useful extension! 😊

Quick diff does not work in snapshot views.

The Changelog section in the extension display inside VS Code shows "No Changelog available".

ClearCase menu entries (Checkout, Checkin, Undo Checkout, Compare with previous version, Version tree) appear in right click menu in OUTPUT window. Not expected as OUTPUT window doesn't contain a file. Other menu entries such Go To Definition, etc. only appear in file windows.

To let the user decide which cleartool executable they want to use, there should be a configuration date for that.
This also could handle webviews (#55 and #57) on a workspace configuration layer.

Version: 1.39.0 (user setup)
Commit: 9df03c6d6ce97c6645c5846f6dfa2a6a7d276515
Date: 2019-10-09T06:58:04.439Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17763

The SCM panel is completely blank with this version of vscode.