I have updated my function that preserves indentation when copying plain text. It now no longer uses Paste[]. @halirutan perhaps you would like to comment? Is this worthy of being added to "the mmase toolbag"? I don't suppose such a thing existed already, right? I would also love to get some feedback on how I am using options. It would be nice to have some kind of uniformity (w.r.t error handling and options) in the mmase tools I suppose. Here is a link
Here is an automated approach. I was able to figure out a way to avoid using Paste[]. The key ingredient here is to use
MathLink`CallFrontEnd@UndocumentedTestFEParserPacket[string, False]
which rm-rf told me about.
I think I am going to find this very useful and I will probably bind this to...
Perhaps you (@rm-rf ) then also know a better alternative to the following (especially considering your package to convert notebooks to mma.se questions/answers).
SelectionMove[First@Cells[nb, CellTags -> "test"], All, CellContents];
FrontEndExecute[FrontEndToken[nb, "CopySpecial", "InputText"]];
@JacobAkkerboom I've used this function since the first version came out and I find it very useful. However there is room for improvement in that the copied code is not like code you have written yourself. The indentation is made up of spaces so if you want to edit the code it's not as easy.
@JacobAkkerboom I also use the SETools palette and personally I think this functionality should be a part of it. Possibly there could be one button that inserts the code in a selected notebook and one button that creates a new notebook with the code in it.
@Pickett ah, thanks for the feedback. Glad you find it useful :). You raise a good concern about the spaces, I had not even considered that. But maybe I have a hacky solution for it.
@Pickett Personally I prefer the idea of a using hotkeys over a palette. Next to that I install packages in $BaseDiretory rather than $UserBaseDirectory. These are reasons why I haven't checked out the SETools package yet, which is kind of a shame. I have also been making some code to automatically backup and verify hotkey files. It actually turns out there is a missing comma KeyEventTranslations.tr in all the recent versions of MMA. I still have to report that. I would love it if some hotkey management could also be integrated in the tools.
@Pickett I think tools for editing hotkeys would help a lot in overcoming some reservations. One thing I always remember is that we are officially not supposed to change the $InstallationDirectory. Another thing is that it hard to guess how we are supposed to manipulate .tr files. The .tr file starts an @@ annotation that MMA does not recognize. You can edit the file in MMA and have syntax highlighting, but really you are editing on boxes rather than plain text. Minor issues that pile up.
I have to go afk for a while, hope to catch you soon
@JacobAkkerboom If this is the reason, then it is really a shame :-) Just install it with automatic script, close Mathematica down and move the package from $UserBaseDirectory to your $UserDirectory.
There is of course a reason for installing the package in your $UserBaseDirectory which is that you very like have write permission there. I'm not sure one can guarantee that for other folders and it would make automatic installing really hard because there are many system, where users are really just users and no admins.
@JacobAkkerboom I will look at your code and probably comment. How about you you add an answer to the SE-Tools post suggesting the inclusion of your function and we see how much feedback we get?
@halirutan thanks for the reply. I will go and install the tools now :). From what I remember from installing the SE-uploader, I had to change some line somewhere in addition to moving the files. But I will see :).
@JacobAkkerboom No, it should work, because it is a self-contained package. The only thing is that the update procedure will install it again in $UserBaseDirectory
After installing version 9, the default style sheet uses Arial font in text and formula cells. So far, so bad. At least one would hope this is done consistently.
But now I see this:
You can see that the default font for TraditionalForm in output cells is Times, which will make such output lo...
Anyone have ideas on how / where to publish long-ish CDF papers of general interest? I have one that's MUCH too big for a Wolfram Demonstrations project. But it has some asynchronous tasks in it and it must be interacted with to be read.
wow. it's a cool blog, tho :) I have one on Kalman filtering as a functional fold. But I do folds over asynchronous observables, so it's gotta be interacted with.
There is documentation of the incompatible changes made to Mathematica with each major release:
Incompatible Changes since Mathematica Version 1
Unfortunately that documentation simply stopped with version 7. Therefore I ask:
What incompatible changes have been made since Mathematica 7?
...
@kguler I edited your question with the code needed to make your answer work in v10. At the same time I imagine a different approach could make use of the v10 functionality as well but I don't have time to dig into it right now.
(Sorry, it's a rather clumsy edit; reformat it as you wish.)
@kguler FinancialData still appears to return plain lists in v10.0. I shall add WeatherData to the Incompatible Changes post; if you suspect other changes let me know and we can figure them out, OK?
Here is an automated approach. I was able to figure out a way to avoid using Paste[]. The key ingredient here is to use
MathLink`CallFrontEnd@UndocumentedTestFEParserPacket[string, False]
which rm-rf told me about.
I think I am going to find this very useful and I will probably bind this to...
After installing version 9, the default style sheet uses Arial font in text and formula cells. So far, so bad. At least one would hope this is done consistently.
But now I see this:
You can see that the default font for TraditionalForm in output cells is Times, which will make such output lo...
There is documentation of the incompatible changes made to Mathematica with each major release:
Incompatible Changes since Mathematica Version 1
Unfortunately that documentation simply stopped with version 7. Therefore I ask:
What incompatible changes have been made since Mathematica 7?
...
