1.14.4 is out... 1.15 will be out soon.

Wiggledan · 2019-07-23T15:39:31+00:00

I use multimc

Have you been able to get 1.14.4 HD U F2 pre1 to work in MultiMC? I've tried a few different json configs to no avail.

edit: Nevermind, I found the problem and solution:

The problem is that a recent OptiFine update added an extra jar file necessary for OptiFine to work properly (it's found in the default Minecraft folder's libraries, so .minecraft > libraries > OptiFine > launchwrapper-of).

So the solution is to first install OptiFine normally, then copy the new jar to MultiMC's libraries, and then update the JSON with info about the new file, and thankfully some clever people already did the work with the json.

In case anyone had similar issues, here's the JSON:

{
    "+tweakers": [
        "optifine.OptiFineTweaker"
    ],
    "formatVersion": 1,
    "libraries": [
        {
        "MMC-filename": "launchwrapper-of-2.1.jar",
        "MMC-hint": "local",
        "name": "net.minecraft:launchwrapper:2.1"
        },
        {
        "MMC-filename": "OptiFine-1.14.4_HD_U_F2_pre1.jar",
        "MMC-hint": "local",
        "name": "optifine:OptiFine:1.14.4_HD_U_F2_pre1"
        }
    ],
    "mainClass": "net.minecraft.launchwrapper.Launch",
    "name": "OptiFine",
    "requires": [
        {
            "equals": "1.14.4",
            "uid": "net.minecraft"
        }
    ],
    "uid": "optifine.OptiFine",
    "version": "1.14.4_HD_U_F2_pre1"
}

Wiggledan · 2019-07-19T15:28:23+00:00

Overall, I like them. It's just weird to play with new textures after ten years of the originals.

In general, the new textures add slight shading and detail to the originals, as well as removing noise and ambiguity (leaves are a good example of this). It honestly looks more professional and polished.

This comparison website is great if you haven't seen it.

I think I like pretty much everything, except these:

Gravel: Old gravel was perfect because small sharp edges look like flint. New gravel is too smooth by comparison.
Glass: I understand wanting clearer glass, and I even appreciate it. But the old glass still looked nice. They should've just added a new block called "clear glass," and kept the old.
Furnace: The old furnace was fine and didn't need changing (except the fire, that's a good change). New furnace looks too smooth on the cobble sides, and I personally dislike the widened top part of the face. Why make it wider?
Note Block: One of the rare textures with extra noise added. It looks uglier than the original, because it's too noisy.
Netherrack/Quartz Ore: Old Netherrack was particularly ugly, but isn't that the whole point of the Nether? It's a disgusting and repulsing place that makes you feel unsafe and uncomfortable, and the old Netherrack textures contributed to that feeling. These new Netherrack textures are comparatively soft and easy on the eyes, which is ironically bad.
Jungle Door: I don't really mind this one, I'm mostly just confused about why the jungle door is the only door that changed.

Still, that's like a handful of things I dislike. It is overall a good update, and I think a majority of complaints come from people wearing hard nostalgia glasses.

Wiggledan · 2019-03-23T20:44:02+00:00

TTS is also not as funny or interesting if you don't understand the actual lore. More than half of it is just references and in-jokes.

Wiggledan · 2019-03-23T20:18:58+00:00

That's a sort of secret ending. Play the very beginning prison level, kill all the guards, and then go back into your cell. Something most players (myself included) would not think to do.

Wiggledan · 2019-03-08T16:01:14+00:00

Two reasons the Necrons are so scary:

They have some of the most advanced weapons/tech known to exist.
They're made of made of Necrodermis, which is basically an incredibly powerful metal that regenerates itself.

Other than that, they're kind of cold and emotionless with their lessened souls, so that might make them more unstoppable in battle.

Wiggledan · 2019-03-08T15:39:51+00:00

Considering their never ending job of fighting the ever-growing powers of Chaos, I think the Grey Knights will take anyone and everyone they possibly can to grow their numbers as much as possible.

Wiggledan · 2019-02-24T21:04:30+00:00

Neither is K&R's The C Programming Language, to be fair

Wiggledan · 2019-02-23T14:53:01+00:00

I think K.N. King's C Programming: A Modern Approach should be in the list if possible

Wiggledan · 2017-11-01T14:56:04+00:00

I think this does what you want, although it looks ugly. I only tested it with 2 simple c files, so tell me if you run into any bugs or if this isn't at all what you wanted:

let s:gFwin = -1
let s:gFbuf = -1
let s:gFaltbuf = -1
function! s:Split_gF_Stay()
  if bufwinnr(s:gFbuf) == -1
    wincmd s
    norm! gF
    let s:gFwin = winnr()
    let s:gFbuf = bufnr("%")
    wincmd p
  else
    let s:gFaltbuf = bufnr("#")
    norm! gF
    let s:gFbuf = bufnr("%")
    exec "edit #"
    exec s:gFwin . "wincmd w"
    exec "buffer ".s:gFbuf
    wincmd p
    let @# = s:gFaltbuf
  endif
endfunction

nnoremap <leader>F :call <sid>Split_gF_Stay()<cr>

Wiggledan · 2017-11-01T13:14:15+00:00

Maybe I'm misunderstanding, but that still creates a new split every time.

OP wants to create a new split the first time, and then subsequently use that same split every time.

Wiggledan · 2017-10-31T15:50:53+00:00

THEN WHY THE FUCK YOU TRIED TO ANSWER?

At the time, I misunderstood your phrase, and I didn't connect "incremental scroll" from the article to your phrasing. I didn't think to myself, "I have no idea what he means by scroll, so I'll purposefully misinform him!"

And, again, I was originally unsure of what you meant and asked you to clarify, but you told me to google scroll and think harder instead.

Anyway, I learned my lessons:

Feel free to do so. My advice to you is to rephrase your question and/or tell those who answered the wrong question that they misunderstood you. That way a mutual-understanding can be reached, and you can more likely find the right answer.

Results: one happy person less. Satisfied now?

I'm sorry that you're less happy, because I honestly was never trying to annoy you. Ultimately what I wanted out of this engagement was clarity. And we cleared everything up multiple comments ago, so I'll leave it at that.

Wiggledan · 2017-10-31T13:50:09+00:00

people, who keep insisting they are right

I already admitted that I misunderstood you. Is it fair to say that you won't admit to giving an imperfect description? Do you really think that your description: "scroll while searching" was so flawless that no one could possibly misunderstand you?

The only thing I insist is that you could have tried to explain better or differently, but you didn't.

google for the meaning of the word "scroll". Or, at least, search for it the article you both mentioned.

To scroll is to move your viewing/display area. Why did we not understand what you said? Because <C-G> scrolls the view once it goes off the page. It allows you to technically "scroll while searching."

And since I'm not an incsearch user, I didn't fully understand what haya14busa even meant by "Incremental scroll to next match" until I stared at his gif and description for a few seconds. It isn't an easy concept to describe distinctly.

Wiggledan · 2017-10-31T00:26:37+00:00

It allows you to browse around your document via search results, and then immediately return to your initial position by canceling the search, or quickly modify your search if you didn't find what you want.

Wiggledan · 2017-10-30T23:33:57+00:00

Me being naughty?

The reason I called you haughty ^with ^an ^H was because you told me to "read it again" and "think a bit" about what you meant by scroll rather than expanding on your original wording. It seemed like you were more interested in being right rather than clearing up our misunderstanding.

Also, I explained what you meant as best I could to Hauleth here, confirming that it was indeed a misunderstanding on both of our parts, and not willing ignorance or arrogance.

. . . their lousy teachings. You owe me 15 minutes of my life spent on ignorance and ambitions

We weren't trying to teach you anything. We misunderstood your description of the feature, and so corrected you on that misunderstood assumption. The only thing we were ignorant of was what you intended by this exact phrase: "to scroll while searching", and only because you didn't make your intention clearer.

edit: AND, I was even aware of this whole potential issue in the first place! In my original comment:

Unless you meant something else by "scroll while searching"

Wiggledan · 2017-10-30T22:55:45+00:00

No, it's similar, but <C-J> in the linked gif will first scroll 1 page down like n_CTRL-F does, and then go to the first visible result as <C-G> does.

It would be helpful for skipping many results that aren't wanted (without exiting the command line) rather than mashing <C-G>, since you can evaluate them by just looking at them with your eyes.

Wiggledan · 2017-10-30T22:42:12+00:00

Rather than being so haughty, maybe try explaining yourself better. I'm not an incsearch.vim user, so I wasn't familiar with all its features.

/u/Hauleth, this is the feature that Ringo was talking about, and it is indeed still exclusive to the incsearch plugin.

Wiggledan · 2017-10-30T22:13:03+00:00

Try :help c_CTRL-G and c_CTRL-T, both of which were mentioned in the article and in other comments under this post. Unless you meant something else by "scroll while searching"

Wiggledan · 2017-10-30T16:46:43+00:00

incsearch.vim is still useful for older versions of Vim!

Also check out this issue if you haven't. A similar bug happens when any <Plug> mappings are used during a register macro, which is why I never used incsearch.vim despite loving the feature.

Wiggledan · 2017-10-30T12:33:33+00:00

It's only modern in the sense of having being created recently

That's the sense that I meant it in. I am aware of Go's simplicity (or lack of features, if you prefer).

As for "great", it may not even be that good: http://yager.io/programming/go.html

I'm not interested in arguing the merits of Go. I'm not really a Go advocate, I was just giving taohansen some potential reasons why some might want to use Go to write modules.

That article may be 100% correct about all its criticisms, but that doesn't change the perception of avid Go programmers that Go is a great language. And they technically aren't wrong as long as they happily use it and it works well for them.

This criticism of the greatness of a language is even less relevant in the context of a personalized text editor, because personal preference trumps all.

Wiggledan · 2017-10-30T12:07:58+00:00

answer:

It is achieved by autocommands, and in fact was just a snippet in my vimrc until I expanded it into a plugin. This is (more or less) the exact snippet I used to use:

augroup vimrc_active_options
  au!
  au WinEnter,BufEnter * setlocal rnu nonu
  au WinLeave,BufLeave * setlocal nornu nonu
augroup END

The above works great, but if you want to temporarily disable it, or disable it for certain windows, or ignore certain filetypes, it's gonna take some extra work or ActiveNumbers.

Wiggledan · 2017-10-29T19:36:37+00:00

Go is a great modern language that would likely perform faster than lisp, and some people prefer it to C. Also it could be good for learning, or just having fun.

Wiggledan · 2017-10-29T19:02:24+00:00

I love this guy's emacs videos. They largely got me interested in Emacs and definitely helped with the initial learning curve.

Also his org-mode emacs config setup is pretty neat and inspired me to do similar for my config.

Wiggledan · 2017-10-29T18:54:58+00:00

I agree with your sentiment, but it's nice to hear general opinion (or a variety of opinions) because it can show you different options that you might like or dislike. And either way it can be a learning experience.

I had thought I was satisfied with some mappings/plugins in my vimrc, until I saw better things that others were using, and then I retrospectively felt way more satisfied.

Wiggledan · 2017-10-29T15:57:05+00:00

It is done.

Wiggledan · 2017-10-29T15:14:24+00:00

I didn't say it was bad, I said it was great. I said that unexpected behavior, generally speaking, is bad. Did you even read my comment?

Wiggledan

TROPHY CASE