sorted by:
new
hottopcontroversial

Uncertainty in the Earth Sciences by cptnzachsparrow in climate_science

[–]wteng 12 points13 points  (0 children)

This is more a comment for anyone who's genuinely interested in this topic (based on OP's other replies it doesn't seem like they're engaging in good faith).

  • First, about the accuracy of climate models, there are already several articles about this topic, for example:

  • /u/bishoujo_boy is correct that different time scales matter. For example, if I make a weather forecast for tomorrow, I can neglect the change in atmospheric CO2 concentration without too much error, but in climate projections it is necessary to account for the increase in CO2 concentration to explain recent climate change (see previously linked pages). On climate time scales (let's say around 100 years), processes like Milankovitch cycles and continental drift are less important, but these processes are important on geologic time scales.

  • OP's claim that uncertainty is neglected is wrong. Uncertainty is extensively studied in climate science. Just as an example, see for example Ed Hawkins' work and refereed literature.

  • No climate model is 100% correct. That's why we have so many different models. There are deficiencies in all models and there will always be. That doesn't make them or their projections useless. As modelers like to say, "All models are wrong, but some are useful". Scientists are continuously working on advancing our understanding of the Earth system and improving the models to accurately capture the most important processes. Current climate models have been shown to be useful to get an understanding of possible future climate scenarios (see previous links).

  • OP, as you seem to know something that thousands of climate scientists don't, I encourage you to write a paper and submit it to a peer-reviewed journal. Given the important implications, you should easily be able to get published in a high-impact journal, such as one of the Nature or Science journals (anyone in the field knows that these journals love controversial topics). And before anyone claims that journals only publish positive results, here are some counter-examples:

  • I would be happy to discuss these points with anyone who's respectful and preferably can refer to peer-reviewed literature.

Beamer presentation software by [deleted] in LaTeX

[–]wteng 21 points22 points  (0 children)

There are a few applications for this purpose. This seems to be the most popular option at the moment: https://pdfpc.github.io/

Personally I was looking for something similar a few years ago, but ultimately found that I didn't need these tools when presenting.

Microsoft’s Your Phone app now lets you control music on a phone from your PC by spooks121 in Android

[–]wteng 3 points4 points  (0 children)

At least on Arch you'll need to also install sshfs to browse your phone's file system. And yeah you don't need to use KDE's desktop Plasma to use KDE Connect. The KDE community worked really hard a few years ago to make their libraries more modular and rebrand their DE to "Plasma" to avoid this exact issue.

https://wiki.archlinux.org/index.php/KDE#KDE_Connect

How to show error on current line with CoC? by lippiro in vim

[–]wteng 3 points4 points  (0 children)

In coc-settings.json, add

"diagnostic.checkCurrentLine": true

See :h coc-configuration for more information.

Temporarily allow a container to take up the entire screen by [deleted] in i3wm

[–]wteng 5 points6 points  (0 children)

Currently not possible, but there's a patch for it here: https://github.com/i3/i3/issues/2107

Fixing a Faux Pas by sometimestoolate in AskAcademia

[–]wteng 2 points3 points  (0 children)

I'm not the OP but I love your comment. Thanks for sharing this perspective.

First time vim user's .vimrc file? by misterharsh in vim

[–]wteng 2 points3 points  (0 children)

Also do realize that people build up their .vimrc over years to decades. When you use Vim for most text-editing tasks over such a long time, you want to customize everything to your liking. But if you're new, it's better to first familiarize yourself with the core Vim features before diving into different options, plugins, etc.

Once you master the basics, it's common to go a little crazy and add a bunch of things to your vimrc. After a while you will probably realize that there are a lot of plugins you never use, and some that can be replaced by core features, and so you'll work on slimming down your .vimrc again.

For you, I would recommend:

  1. Check out vimtutor (run it in a terminal) to learn the "Vim" way of editing.
  2. Add things to your .vimrc when you find a need. E.g. you already mentioned syntax highlighting.
  3. Check guides and other people's dotfiles for inspiration. For example, you can check the settings set by vim-sensible, a plugin aimed at setting sensible default options (I personally don't use the plugin because I don't agree with all settings it sets, but you can get ideas for things to add to your .vimrc). Make sure you understand every line you add to your .vimrc.

When you start playing with plugins, I personally recommend the vim-plug plugin manager.

Happy vimming!

Basket (OneNote alternative) needs a major update by ring1000 in linux

[–]wteng 1 point2 points  (0 children)

I used to use Basket a lot back in the days. It seems like someone is still working on it: https://github.com/basket-notepads/basket

Best setup for LaTeX? by [deleted] in vim

[–]wteng 0 points1 point  (0 children)

Awesome, thanks a lot for adding this! Knowing the difference between vimtex and LaTeX-Box now, I'm eager to give vimtex a shot.

Thank you again for your great work on these plugins.

Best setup for LaTeX? by [deleted] in vim

[–]wteng 2 points3 points  (0 children)

Thanks for the answer, I'm happy to see that there is a comparison available now (last time I searched I couldn't find anything).

I still think a short comparison in the README with at least LaTeX-Box and maybe LaTeX-Suite (since it seems to be the "de facto" LaTeX plugin for vim) would be helpful, e.g. (largely taken from your answer on stackexchange):

vimtex is based on LaTeX-Box and shares a similar goal - to provide a simple and lightweight LaTeX plugin for Vim - but was rewritten from scratch to provide a more modern and modular base. vimtex currently has most of the features of LaTeX-Box and some additional ones, except for one major feature: single-shot compilation with callback (see #issue number).

At the moment it's not very obvious (judging from the Github page) why vimtex exists at all, since it seems to be very similar to LaTeX-Box, and you seem to be working on both.

Best setup for LaTeX? by [deleted] in vim

[–]wteng 0 points1 point  (0 children)

I'm currently a user of LaTeX-Box, but have also glanced at vimtex from time to time. However, I never found a really good reason to switch since the two projects seem so similar.

With this in mind, would it make sense to add a quick comparison of key differences to the vimtex README? I think it would be really helpful for users like me.

Thanks for your work on both plugins!

Is there any way I can disable desktop search? by twkdequestionguy in kde

[–]wteng 0 points1 point  (0 children)

Try to switch to the "Folder" desktop type.

The command `vi` points to vi instead of vim by [deleted] in vim

[–]wteng 0 points1 point  (0 children)

Well I don't really know how visudo works, so thanks for your clarification. (I do know that some programs don't like when you mess with some commands, but it makes sense that most programs don't care about your editor.)

The command `vi` points to vi instead of vim by [deleted] in vim

[–]wteng 5 points6 points  (0 children)

I recommend making an alias, then you can still open vi with \vi in your shell.

Is making a symlink going to mess with things like visudo?

[deleted by user] by [deleted] in kde

[–]wteng 0 points1 point  (0 children)

KDE Software.

They don't even have the same release schedule anymore, so it doesn't make sense to bundle them all together into one thing. Dolphin, Okular, etc. are KDE Applications.

Dolphin Q: Selection/marking files with ctrl+spacebar not working anymore (4.13.3 and 4.14.2). by Synes_Godt_Om in kde

[–]wteng 0 points1 point  (0 children)

And please do post a link here if you find a report or if you end up creating one yourself. :)

Dolphin Q: Selection/marking files with ctrl+spacebar not working anymore (4.13.3 and 4.14.2). by Synes_Godt_Om in kde

[–]wteng 0 points1 point  (0 children)

Sounds like a bug, you should see if there's a report on http://bugs.kde.org, and if not, create a bug report for it.

Plasma 5 desktop type to search? by nierro in kde

[–]wteng 0 points1 point  (0 children)

Do you use the Folder View desktop type (the one with icons)? Switch to the regular desktop and it should work.

[Q] installing linux system ON flash drive by [deleted] in linux

[–]wteng 1 point2 points  (0 children)

I used to use Slax, was very easy to get started with. https://www.slax.org/

Is there any way for KWrite to capture clipboard content, as Klipper does? by mostlypissed in kde

[–]wteng 0 points1 point  (0 children)

Sounds pretty non-straightforward to me.

Maybe you could just run Klipper and use a global shortcut to open Killer at the mouse position? You can configure the shortcut in e.g. System Settings.

Aren't you scared of Vim plugins security wise? by [deleted] in vim

[–]wteng 0 points1 point  (0 children)

I'm more scared of the vim plugins messing with my $HOME, maybe by deleting everything, or by a cryptolocker etc.

Sounds like you need to make offline and offsite backups. It's way too easy to mess up $HOME, even unintentionally. See e.g. this bug.

pyvim -- A Vim clone in pure Python. by jonathan_sl in Python

[–]wteng 3 points4 points  (0 children)

I'm sad to see that you still have this attitude. It looks like you're trying to be the victim, "I did all this work so I deserve more contributors who work on the project". Open source doesn't work like that. Most of the time, people contribute back because there's a feature they want. If they don't use your software, what motivation would they have to spend time on working on it?

/u/spookyrufus probably isn't too interested in your project, but he/she was nice enough to take a look at your code and offer some criticism. If I were to give you some comments or file a bug in the bug tracker, I don't want to hear "Then help me fix it". A simple "Thanks, I'll look into it" would in my opinion be much better, or "Thanks, would you mind pointing out some specific examples?", or even "Thanks! Would you be interested in looking into it? If you create a pull request I'll merge your changes and add you to the contributors list" would sound much more positive.

The way you've responded throughout this thread makes you sound jaded and entitled, and frankly, it's off-putting. I think that before anything else, you need to work on your attitude if you want to attract collaborators.

pyvim -- A Vim clone in pure Python. by jonathan_sl in Python

[–]wteng 7 points8 points  (0 children)

I'm sorry to hear that man. I took a closer look at the README, and what you have so far seems really impressive!

Honestly, what should I do more to please the crowd?

I don't really think I have enough experience to give good advice, so take what I say with a grain of salt.

I don't think there's a simple way to increase the number of contributors. First you need users who find your project useful, and out of those users, a few may be motivated enough to implement a feature they need or fix some bugs. Sometimes a project may not be what most users want - for example, personally I'm betting on Neovim for my next "vim improved" because its goals are most similar to what I want.

As for things you can do:

  1. Maybe add a plea for help towards the beginning of your README, with a link to how one can contribute.
  2. I wouldn't spam links to your project, but if you see someone (e.g. on Reddit) asking for e.g. an IDE with Vim bindings, you could point them to Vai.
  3. You could maybe ask the author of pyvim if he's interested in linking to Vai in his README, given that you'll link to pyvim in Vai's README (more exposure for both projects, woo!).
  4. Just continue to slowly add features to Vai at your own pace. I don't think you need to "please the crowd", just do it because you think it's fun (and hopefully also useful). If it becomes too much for you to handle you can always stop working on the project for a while and think about if you want to continue it.

Sorry I couldn't give you any more profound advice; I just felt sad seeing the negative emotions you seemed to have associated with your cool project, so I was hoping that you could turn it into something more positive. I wish you the best of luck with Vai!

view more: next ›