What is Reddit's opinion of SciTE?

From 3.5 billion Reddit comments

This has very little to do with np++. The scilexer.dll mentioned is part of the Scintilla open source project, which is where most of np++'s functionality comes from. There are several other editors out there that use the Scintilla toolset, all of which are subject to the same vulnerability as np++.

If you're worried/find you have a modified dll, just go compile your own from Scintilla source. That's what the CIA did...

I only looked at the website and screenshots, so these are just early impressions:

• There doesn't seem to be much syntax highlighting going on. My guess is you're using scintilla. Something like this would look way better.

• You seem to be using a intermediate language to generate GLSL, are there any plans to generate HLSL or target other GLSL versions?

Well tbh none compares to N++ in my opinion. Maybe because I am used to it. I have tried many other editors, but could not get used to them. I see http://www.scintilla.org/SciTEDownload.html this is available also for Linux. So theoretically it's already very similar to a barebone N++. I will give it a try maybe. Trying to recompile it with N++ icons and so on

Three virtual desktops with Scite, RiskOfRain and my browser / engine infos / wiki pages open using SharpE as my windows shell (which already comes with the virtual desktop feature). I basically just play RoR, kill a few waves, swap over to Scite, code a few lines, swap back and kill the newly spawned mobs while thinking about problems or bugs in my code and swap back. Pretty relaxing after you have the basic item setup (infusion, 100% crit rate and so on).

When you have alot of barbed wire stacks, mobs will start to die when they enter your screen. Flying mobs (like those jelly thingies on the very first maps) mostly die on the same two places top left/right from you and their chests (all mobs elite artifact and elite drop chests artifact) will drop on both side's on the same place. When you go there and press E, select a item and press E again it does that for all boxes that are on that spot already. Which isnt limited i guess.

Look at the Scintilla text editing component. Basically it's a ready-made widget that you can integrate into your project.

You could also create your own text editing component (handling word wrapping, font drawing, etc.) but it quickly gets very complex.

Hi, I use linux (Debian) as my programming environment as well. I mainly use SciTe as my main code editor. I've also used CodeLite and QtCreator.

SciTe is a great text/code editor that offers syntax highlighting, some compile options/features, and output/debug tracking. I use SciTe as my everyday text editor as well as throwing any bit of code I have at it. Large language listing for syntax highlighting. (Python, C/C++, C#, Lua, PHP, etc)

CodeLite is an more advanced IDE that also offers code/function completion. C/C++ only

QtCreator is more of an IDE for building GUI applications with the QT Framework, but you can also just write pure C++ in it as well. C/C++ only.

"^[^Name].*" happens to work for the sample text because it matches lines that do not start with any of the characters "N", "a", "m" or "e".

It seems that the regex engine implemented in notepad++ is this: http://www.scintilla.org/SciTERegEx.html (according to its online help) which supports very minimal regular expression syntax.

Cheers.

http://www.scintilla.org/SciTEImage.html - it takes a while to get setup just the way you like it, and I am still learning. All in all its a great free text editor with code folding and support for all the Things. You can save a "session" so you don't have to reopen files from all over the place and best of all without any Intellisense its fast and furious and never helps wrong.

Another good one is SciTE (http://www.scintilla.org/SciTE.html). I like it because it's quite a bit lighter weight (there's a single-file portable version!), but it still has great regex find and replace, folding, and highlighting. Plus, it works on Linux too.

I dout your going to be able to make something better then ad blockers already out thee where 100's of hours have been put into them. Also notepad++ can do everything listed for SciTE-based

Hmm, you might just have to use either

SciTE4AutoHotkey is a lightweight and easy to use SciTE-based AutoHotkey script editor. It provides:

​

• Syntax highlighting
• Calltips (also known as IntelliSense)
• AutoComplete
• AutoIndent
• AutoHotkey help integration
• Abbreviations
• Editing macros
• Interactive debugging
• Tools for AutoHotkey scripting
• Powerful extension mechanisms
  

Or

Regular Notepad++ with syntax highlighting on.

Gonna fix up your title for you "Ad Closer aka Ad blocker" in case other people are confused.

I'm sure you'll use some variant of this for blocking ads via browser. I'm really not quite sure what you'll do to be honest but I hope this helps:
https://www.autohotkey.com/boards/viewtopic.php?t=47281

Just reconfigure it to target browser instead of spotify and then do your magic.

Driving the Great Ocean Road in Victoria and there was a "DRIVE ON LEFT IN AUSTRALIA" sign at each entrance to the main road. Does New Zealand have these now on heavily touristed roads?

Sign image

update After 9 hours of working through the night this is what I have so far. Right now, it scans the mods folder and finds any zip files or folders that contain a info.json file. It unzips the .zips to a temp directory and parses through the folder structure. The tree on the left tool window is filled out with the right structure and icons. If you double-click on a lua file from the tree, a code window opens that has nifty features such as syntax highlighting, line numbering, and (eventually) code folding and auto-complete. (Thanks to the guys over at Scentilla for the text editor and jacobslusser for the .NET wrapper! Saved me a TON of time!)

Even with the small amount I have done, I can see some things that need to be optimized. For instance, the way I have it set up now, it completely decompresses every zipped mod into the temp directory and creates a folder structure. That adds some time to startup, even though I use a second thread and save it to a SSD. I would imagine it would be a bit slower using a regular HDD. What I plan to do in the future is have it read the contents it needs to from the .zip file (mainly the info.json, but possibly some others) into a memory stream to get the data. Then it will only completely unzip the file if you start to edit that specific mod.

Anyway, I'm off to sleep after I get done with a few TODO comments so I don't forget any ideas I've thought of in my sleep-deprived brainstorming. Feel free to ask questions or leave suggestions!

uhh, I would have said download this, uncompress it, and run the SciTE binary.

But I just tried that and for some reason trying to exec the SciTE binary nets me a "No such file or directory" which is weird. What a pile of shit. Just use gedit or vim or something.

> On a separate note, could you explain some of the best practices (or point me to any resources) about building out a script? I've been just copy-paste ing my script to test things out as I built it so far.

There are no one "best thing to do", it all depends on your work flow. If you're used to working in a GUI environment, you're probably not that used to doing things in a terminal.

I suggest that you find an editor (it doesn't have to be a full-on IDE, but it can be) which allows you to run your script directly from the program.

For example, I write most of my Python code in SCiTE, which is a text editor based on the same core that Notepad++ uses. I write the code in the editor and whenever I want to run it I press f5 (okay, technically I've bound ctrl+3 to run the code, but I think that f5 is the default) and it'll run inside of the text editor.

I also constantly open up new Python REPL instances (what you'll get when you simply type python in a terminal/command window) to try new things out. I also occasionally run my scripts in a terminal using python -i scriptname to get into interactive mode.

I also have my own library of helper functions to quickly try new things out without having to manually import a bunch of stuff every time I start a new Python window. For example, I have a function ppd(object) that will call pprint.pprint(dir(object)), which is super useful when exploring a new library where you don't want to have to read the entire documentation.

As some other people have mentioned, you should definitely learn to use functions such as type, vars, dir and pprint.

Those are all fine for me. I used to use jEdit quite a while ago (like 8-10 years), keeping a copy on a flash drive since it was Java-based and would run wherever*, but I really don't care for it that much, personally. There are much better editors, at least for my taste.

I tend to use vim on my own system at home for minor and moderate text editing. I've never really gotten into or cared much for emacs, though I have used it.

I've not really used SCiTE, but it would probably be a good one for me (I like the cross-platform nature between Win and Lin) and I may look into it a bit more. I know it's the upstream for Notepad++. (CORRECTION: It uses the same editor component, Scintilla, which is part of the same project, more or less.)

But whatever text editor I install also gets used by kids for programming classes, and Notepad++ still fits the needs there the best judging on ease of use, intuitiveness of interface (the Office 2003-like toolbar w/ buttons), and convenience of feature set. I'm just starting to feel wary about it based the capriciousness (and sometimes poor judgement) of the dev, that's all. Not quite ready to jump ship. But I'm edging towards the lifeboats — or at least eyeing them up.

* ^(I honestly don't recall if there were separate Windows and OS X executables at the time, but I know it was portable.)

Notepad++ is often recommended, but I would instead recommend SciTE which is built from the same core as Notepad++ but works better.

It's easier to configure (just one text file with all the config, plus another one for each language), less buttons on screen and most important: there isn't a massive spacing between each row, which is what ruins notepad++.

I see one big problem: >All of the programing assignments given out I complete very quickly

and >I have a really hard time just writing out code on paper and knowing it will working without testing it out slowly

"Very quickly" is relative. I thought I was quick in high school, looking back only to think of how slow I was.

Get rid of Eclipse. Get rid of code completion. Get rid of everything that assists you. Use something like Scite or Emacs or Vim. They have nice syntax highlighting - something that, honestly, is worth it - however, they insert (nor remove) nothing for you.

In AP Comp Sci I had to write most of my code by hand, timed. I hated it, but it made me better. If your exercises are boring, well, make them harder for yourself. Always write in input sanitation checks, make it robust, make it do something cool. Nearly no school project is "production" level.

Project Euler is a good math-challenge website involving programming.

What kind of CS theory have you done to get to your 3rd year...?

Well, we can almost certainly whittle it down to an editor using Scintilla judging by the look of the line numbers and cold folding. The most popular on Windows being Notepad++. But you may also want to check out a list of editors that use Scintilla.

I just thought I'd share, ya know?

Odd thing is, Notepad++ is based on Scintilla, which is also what SciTE (*nix app) is based on. But while I lurvs Notepad++, I'm not much of a fan of SciTE.

Assuming you installed Python 2.7.

Go to Start -> Run -> type "cmd".

At the command prompt type "python", this should splash the version number of python and another prompt which starts with ">>>". If you get this far then you have the Python interpreter successfully installed.

To run a program in Python you exectue the following command at the terminal "python /path/to/your/file.py" this runs file.py in the Python interpreter. You could also use an editor like Scite or PyCharm or WingIDE which wrap the editing and executing up up in GUI.

All of this is completely independent of whatever version of Windows you are running.

i'm using SciTE and it has an abbreviations feature that i use for storing snippets.

with that said, i'm on windows. but operating system aside, i personally prefer code snippets managed by the text editor either directly or via plugin. but that's just me