Community

The checkbox is randomly unticked. "Randomly" because I yet have not grasped a pattern on how to reproduce this. It happens when working with the very same TextPad window/instance - it's not a problem of closing TextPad and then starting a new instance. Opening new documents in there might be a ...

They should employ you for doing QA.

I wonder what makes you think no other other variant fails. I don't understand: we're talking about running a program thru TextPad , not the command line itself. Hence I consider all your other 3 variants of inappropriate, as they do not relate to the goal. The command in there is C:\Windows ...

As a TextPad Tool of the Program type http://i.imgur.com/9KHFKMJ.png it fails to run http://i.imgur.com/bOLlKq6.png This variant only, of course. And by CMD.EXE I was implying the full path to the executable, as in http://forums.textpad.com/viewtopic.php?p=42706#42706 (speak: i.e. C:\Windows ...

Have you tried running it thru the command prompt directly?
cmd.exe /c script.bat

ben_josephs wrote:TextPad is still an MDI app
...
if document tabs are turned on

I thought "this implies I can disable tabs - but where" and then tried menu "View" > "Document Tabs". Wow, never recognized this. Thanks alot. Much better now.

It's all about asking any question at all.

It's poor heuristics that concludes José is more likely than José. You seem to never have written code for an encoding sniffer, especially for european texts - it's far from being easy. The Win32 API fails at this as well. (@ bbadmin : if you're actually using IMultiLanguage2::DetectInputC ...

It just confirms what I already found out:

AmigoJack wrote:I can only assume that á alone is not enough for Textpad to think the encoding is meant to be UTF-8 - it just thinks it's ANSI. But my two additional Katakanas are enough as an indication to UTF-8.

TextPad 4 still supported MDI and its huge advantage was that I was able to freely position all windows inside TextPad. With TextPad 5 this was dropped, and I always wondered which reasons for this apply: supporting MDI causes too much work it was because of introducing appearance/skins/themes other ...

At that point, heuristics are used to determine the codepage of the file. When opening a file (CTRL+O) I have a combobox to select an encoding [1] - why not having it also for the "Run" command, and the "Find In Files" command, which most supposely has the same dilemma? It can never surely know ...

07.Nov.2016 04:51 Mind timezone settings. For me the post was created at 02:51 +0000, so you seem to use +0200, and we both don't know which timezone the author was using. To directly link to a post use this http://forums.textpad.com/templates/subSilver/images/icon_minipost.gif icon, which you find ...

CMD is Windows, and Windows' linebreaks consist of \r\n. I'm sure Textpad has its own conventions when interpreting output, so don't rely on that.

Keywords #1 are displayed with blue background and white text, Keywords #2 are displayed with white background and black text. If your selection background is black and the text color wouldn't change (speak: syntax highlighting would still apply), you'd have a problem with keywords #2 and their ...

Because I see it the same way: either syntax highlighting or text selection, not both at the same time. A bug is something that is not working as intended, and syntax highlighting in your text selection was never intended.

As we found out in http://forums.textpad.com/viewtopic.php?t=13008 no matter which setting you use in Configure > Preferences > Document Classes > * > Document class options > Default encoding , it has no effect. Saving a file with an á as UTF-8 file and then re-opening it won't use the default en ...