I'm having some issues with my default.magic file in clearcase when adding files to clearcase.
When I go to C:\Program Files (x86)\IBM\RationalSDLC\ClearCase\config\magic the default.magic file is not visible in windows explorer or by doing a dir in a cmd window.
However I can open the file in a text editor and make changes to it. (Via the open dialog).
What is going on? Is it possible clearcase can't find its own file?
I am not sure why the default.magic file, wouldn't be visible, but it is best to leave that default file untouched.
As explained in Evaluating multiple magic files, you can define multiple magic files for you to test.
In "About the ClearCase Magic file", you would, for Windows (including CC7.1+) create a cc.magic file (in the same directory as the default.magic file). And that file would be visible enough.
Related
in InstallShield 2011, I cannot modify file permissions under Application Data -> Files and Folders. Whenever I right click on items, it shows grayed out menu buttons. I can't even delete existing entries.
In a bat script later in the installer, I can't copy over certain files because I don't have the right permissions so the installer fails when trying to reference files in BackupFiles. For some reason all the other files get copied over just fine; I can't modify those file's permissions either. I read online that you have to click the "Properties" button in that context menu to change permissions.
My version is InstallShield 2011 Premiere Edition Version 17.
I don't understand why this is grayed out. The source files do not have any restrictions on them so it must be the installer doing something related to permissions.
That boxy orange overlay on the folders and files indicates that these are coming from a Dynamic File Link. Because these files aren't actually added to your project, not all configuration options are available. You might have to edit the permissions on the source files (before build), or change your project to statically include all or some of these files. Given the size of that tree, changing it all to static could be a bit tedious. Changing parts of it (by editing the link exclusions) might be a good middle ground.
Or you could better determine what's going wrong and see if you can address it in the batch file. Assuming this is InstallScript (rather than InstallScript MSI), the entire setup along with any processes it launches should be elevated. So I'm having a hard time guessing what could go wrong. Perhaps a read-only flag? Perhaps use a tool like process monitor to get more information on that, and see if you can add a call to attrib -r, or cacls, or whatever.
I'm on a company laptop and appdata has restricted storage space. An initial google showed there isn't really any settings to move directories. I was thinking of simply copying relevant directories i.e. \AppData\Roaming\Code to somewhere else, then creating a hard symbolic link (junction) with the same name and then point it to the same location
i.e. in command line:
mklink /J C:\Users\me\AppData\Roaming\Code C:\myFolder\Code
I played around with moving the whole appdata folder (right click on roaming/local/locallow then click on properties then location tab then change directory). I managed to only move half the files over. it seemed to work until i restarted and it caused chaos.
I don't want the same thing to happen again with vscode. (that said I haven't tried using a symbolic link for appdata
what is everyone's advice? can i create a symbolic link and have everything work fine? or will i cause more chaos again? if it works for vscode, i'd like to do the same for appdata too
Portable Mode in Visual Studio Code
You can use Portable Mode: After unzipping the VS Code download, simply create a data folder within Code's folder
After first launch 2 folders will be generated inside:
..data\extensions
..data\user-data
Then you can copy your company folders with files from
%APPDATA%\Code\User\
Then copy the extensions directory to data:
%USERPROFILE%\.vscode\extensions
Portable mode is not supported if you install VS Code. It is only supported if you get the ZIP download.
Symbolic links should work, but you can also tell VS Code to use a custom extension and user setting location with the --extensions-dir and --user-data-dir flags respectively
$ code --extensions-dir "/User/me/vscodeExtensions" --user-data-dir "/User/me/vscodeData"
There are some key limitations to this approach, such as extension updates not working. We are tracking support for a truly portable VS Code here: https://github.com/Microsoft/vscode/issues/329
Recently I scaffolded a project with webapp generator. It created two files .gitignore and .gitattributes. Both show a file extention of type Text Document But when I press F12 to edit any one's name then it has empty name. Here is the snapshot:
My question is why don't window show the name as .gitignore?
There is nothing special with those files. This visual guide may help you.
Also in Windows 10 you may simply try this option in View Tab of Folder Explorer:
After looking and reading closer, it seems that the "problem" is that with the default settings of Explorer "known" file-name extensions (like e.g. .txt) are just not shown.
So if you name a file .txt (full file-name) then it will show up as empty and with no name.
Dot-files are not having any "extension" to their file-name. The full file-name of e.g. the Git ignore file is .gitignore.
It comes from the Unix world where file-names doesn't have to follow the DOS and Windows name.ext scheme, and means that the file is hidden.
Windows since long allows arbitrary file-names as well, but in a name.ext scheme such files doesn't have a "name" only an extension.
Windows interprets .gitignore as an empty file name with the extension "gitignore", and thus shows an empty name be default. To properly see its name, open the folder's properties and check the "Show All File Extensions" option.
I don't have an answer, but I have a preference. I'd prefer not to show all extensions just to be able to see my .gitignore files in Windows10 file explorer.
I'm hoping to extend OP's question by showing I DO SEE .babelrc and .eslintrc, and w/o seeing all file extension setting being set to "on".
It seems, on my own system, that the associations for BABELRC and ESLINT(RC|IGNORE) are, maybe, set automatically by VSCode? In any case, why can I see those "." files, while the in.json is showing with hidden extension, but I can't see .gitignore?
i have gone through the this post and it says that the files take the automatic behavior of the windows to open the .cs and .sql files.
in my case when i open these files from a folder it opens up correctly in vs and sql server for .cs and .sql respectively.
Can anyone tell me how to open a file in a shelve in any editor other than notepad?
i have also checked the file types tab in folder options.
I believe you are using the VS Shelveset Dialog which is modal - maybe that's the reason "they" designed the View function to spawn a new process of notepad. It's unfortunate because for some file types, the editor is not VS but it will still bring up notepad. This is consistent with all other TFS related operations in VS. with changesets, you can view files in VS or other editor, when you look at any non-modal dialog (history for a single file for example)
So unfortunately without hacking around there's no way to change this behavior.
I'm using TortoiseHg v2.2.1 with Mercurial 1.9 in WindowsXP. How do I configure TortoiseHg to view a file based on the application Windows has associated with its extension?
For example, if I have a .docx file in the repository and I'm looking at its revision history, I'd like View at revision... to open the selected revision in MS Word. Likewise for other binary file types like ppt and xls, which I can't view using the default text editor or kdiff3.
Can I leverage that Windows already knows what program to use to open certain types of files or will I have to manually configure each file type of interest within the Tortoise config files?
I've found several SVN scripts in the TortoiseHg\diff-scripts folder that look like they solve a similar problem for diffing binaries rather than simply viewing them, but those don't seem to be activated and I'm not sure what if anything I need to mod in the MergePatterns.rc or Mercurial.ini files to make this all work.
To make "View at Revision" use whatever program is associated with the file's extension, try this trick: In the "Global Settings" in the "TortoiseHg" section, enter start "" as "Visual Editor". Note the empty "". This is necessary so that start will not use the file name, which gets passed in quotes by TortoiseHg, as the window title.