Exclamation mark on .xlsm file - xlsm

i've prepared one excel file with Visual Basic code. It was saved with .xlsm extension. And now the excel icon is appeared with exclamation mark that is irritative.
Can I remove that exclamation mark from the icon?

save that file with .xls extension.you can remove exclamation mark
With the introduction of Office 2007, Macro enabled worksheets saved as .XLSM files show the exclamation point as part of the icon. This is not to show that it is an error or that it is dangerous, only to inform you that it contains macros. “Feature” or not well thought out placement of punctuation? It’s completely normal, and everything is fine as long as you trust the document and/or created the document and macros yourself.

Related

Format only pasted code segment in VSCode, not entire document

Is there a way to do so? I find a lot of my time is taken up correcting indentation formatting in VSCode after pasting, because it seems to sometimes take the source indenting and apply it at the destination (so the entire pasted code block is at the wrong indent level) or worse, just mess up indents entirely (no idea what's going on here) and I need to manually fix every line.
Example use case, for single PHP files which contain PHP, HTML, and Javascript, I often only want the pasted Javascript block to format nicely. Turning on "paste on format" will format the entire document, often times making the PHP sections awkwardly arranged.
I know that VSCode has "format on paste" in settings, but this formats the entire document. How can I format only the pasted code? Is this even possible?
Thank you
I am not certain whether you're fine with this roundabout solution, but you can format selection with Ctrl+K Ctrl+F (see official vscode site for more detail). So rather than turning on format on paste you can paste and then reselect it and do the shortcut above.
If you're not satisfied with this method, you can try using a vscode extension that was given here under a somewhat similar copy and paste problem

Zoom/focus on a region/part of file in vscode?

Let's say I have a giant markdown file and want to edit one section, or a giant python file and want to edit one function. Is there any way to bring out that region of the file into a separate editor?
Desiderata:
Find (⌘F) and "add selection to next find match" (⌘D) should only go over focused contents.
Changes should appear in original file in the filesystem for version control purposes.
No text outside of focused section is visible anywhere.
Bad solutions:
'Fold all & unfold one' works ok in markdown, but e.g. if there is section text at a parent section, then there is no way to hide it. And ⌘F goes outside of it.
A temp file clutters the git logs if I commit as I go.
Extension keywords (no results):
File window
File region
Zoom to part of file
(Iterm2 has a feature like this for focusing on the last command output.)
It seems there is no good solution as of May 2021.

How to: Go to file (#) Go to for symbol in the same dialog

I am missing this feature from Sublime Text so much. Go to Symbol in Workspace feels so close to it and yet so far away.This is very useful in the following examples:
You have many classes that have the same symbol/function name, Pre-filtering the file lets you jump to the exact definition very fast
You know the name of the file, but you are not sure about the exact symbol/function name. Fuzzy searching it is super fast
You want to quickly preview the available symbols/functions in a given file
Here is a sample video demonstrating this feature in Sublime Text:
https://youtu.be/48f3N0hCaBU?t=109
If this is not currently possible, is it possible to implement as extension?
This is being added in v1.44. See https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_44.md#navigate-from-files-into-symbols
You can now continue to navigate into symbols of a file result simply
by typing #. For the file that is currently selected, all symbols will
appear and the editor will open in the background to reveal the active
symbol.
I created an extension that provide similar functionality:
https://marketplace.visualstudio.com/items?itemName=Cmacu.gotoanything

notepad++ deleted files popup

When I delete file notepad++ displays the below message:
The file "D:\xxx.txt" does not exist any more . keep file in the editor?
Can I stop this message and silently remove deleted files from the editor?
Message box with the question is displayed unconditionally. There cannot be anything done about removing it simply by chaging configuration.
If you have necessary programming and app building skills and you wish to remove it, search for Notepad_plus::doCloseOrNot in Notepad++ source file <source root>\PowerEditor\src\Notepad_plus.cpp and modify the code accordingly – for example to always return No (=do not keep file in editor) without showing a dialog. Then build Notepad++ from these modified sources so the change will be there.

iphone sdk Localizable.strings files displaying incorrecting in xcode 4.1 after upgrading

After upgrading to iphone xcode 4.1 build 4B110F all of my localizable.strings files are showing up as gibberish in the xcode editor. I created these files using UTF-16. I can not find a way to tell the editor that they are UTF-16. I am able to view the Localizable.strings files by viewing as a property list, but if I view them as Source Code, I see gibberish. I like to translate the entire localization.strings file and paste it into the editor. I don't want to have to cut and paste one line at a time in the property editor. There should be some way to tell xcode to show the file as UTF-16. Does anyone have any ideas?
I tried removing the files and re-adding them. I used to get prompted for the UTF type, but it does not do this any more.
You can find the text encoding setting for a file in the Utility area of Xcode 4.1. The utility area is the right-handside lateral area.
In the utility area, look for and select the first pane, named "File Inspector".
There, you will find the text encoding in the "Text Settings" block. Expand if necessary using the triangle.
I had this same problem. I was able to work around it (without much actual investigation) by simply opening the previous string files in TextWrangler, then copy from TextWrangler and paste into XCode4's view of the string file. Things seem to be working fine as a result.
To fix XCode 4.1 UTF-16 encoding issues:
1: Open the file you want to change
2: Put your cursor into the file, which will give the editor focus (VERY IMPORTANT).
3: Proceed to look under the Utilities Pane (very far right) for Text Settings and use the Text Encoding drop down to select UTF-16 or whatever other encoding you want.
If you forget step 2, and only highlight the file in the Project Navigator, you will not see encoding options.