Skip to content

Instantly share code, notes, and snippets.

Alejandro Exojo suy

Block or report user

Report or block suy

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
suy / threadpool-lingering.cpp
Created Mar 23, 2018
QThreadPool lingers till the end of the app, for good or bad
View threadpool-lingering.cpp
#include <QtCore>
class TurtleRunnable : public QRunnable
void run() override {
for (int i = 0; i < 15; ++i) {
qDebug("Tick %i", i);
suy / problems.adoc
Last active Jul 30, 2018
BTRFS "no space" problem
View problems.adoc


# df -h -x tmpfs
Filesystem      Size  Used Avail Use% Mounted on
udev            7.8G     0  7.8G   0% /dev
/dev/sda1       9.4G  6.1G  3.3G  66% /
/dev/sda2       923G  439G  482G  48% /home
# btrfs fi show
Label: none  uuid: 1c8212fb-88ff-4f39-912a-5178a3547e6c
View gist:2ef689ec42d71e3633d81f673ade0382
<manuelschneid3r> does QString("text") allocate exactly the necessary memory or do i have to squeeze?
<suy> qout: { QString t("text"); qDebug() << t.capacity(); }
<qout> 4
<suy> qout: { QString t("a much, much, much longer text"); qDebug() << t.capacity() << t.size(); }
<qout> 30 30
View capture-shared-pointer.cpp
#include <QtCore>
#include <memory>
int main(int argc, char** argv)
QCoreApplication app(argc, argv);
auto p = std::make_shared<int>(42);
auto t = new QTimer;
suy / output.adoc
Last active Jul 16, 2016
runtimepath after nvim-qt startup
View output.adoc
/home/alex/personal/configs/dotvim/init.vim|| 1
/home/alex/personal/configs/dotvim/bundle/pathogen/autoload/pathogen.vim|| 2
/usr/share/nvim/runtime/autoload/provider/python.vim|| 3
/usr/share/nvim/runtime/autoload/provider/pythonx.vim|| 4
/usr/share/nvim/runtime/autoload/provider/python3.vim|| 5
/usr/share/nvim/runtime/autoload/remote/host.vim|| 6
/home/alex/personal/configs/dotvim/bundle/submode/autoload/submode.vim|| 7
/home/alex/personal/configs/dotvim/bundle/lastnextprevious/autoload/lastnextprevious.vim|| 8
suy / appveyor.adoc
Last active Jan 2, 2016
Notes on using Appveyor
View icon-workaround.adoc
:header: I'm on GitHub!
:star: :star:
:header: Somewhere else.
:star: icon:star[]
View gist:63e96915d859183e8c39
SYSCALL(args) = return
thread_selfid(0x6000003165C0, 0x60000040B630, 0x6000020F4B80) = 53886 0
csops(0x0, 0x0, 0x7FFF56778278) = 0 0
issetugid(0x0, 0x0, 0x7FFF56778278) = 0 0
shared_region_check_np(0x7FFF567761B8, 0x0, 0x7FFF56778278) = 0 0
stat64("/usr/local/lib/libosxfuse_i64.2.dylib\0", 0x7FFF56777078, 0x7FFF56778278) = 0 0
open("/usr/local/lib/libosxfuse_i64.2.dylib\0", 0x0, 0x0) = 3 0
pread(0x3, "\312\376\272\276\0", 0x1000, 0x0) = 4096 0
pread(0x3, "\317\372\355\376\a\0", 0x1000, 0x8C000) = 4096 0
mmap(0x1095C0000, 0x1F000, 0x5, 0x12, 0x3, 0x8C000) = 0x1095C0000 0
View gist:99d2efc63a8711e4bdf5
All packages are already installed and there is nothing to restore.
NuGet package restore finished.
1>------ Build started: Project: ZERO_CHECK, Configuration: Debug Win32 ------
1> Checking Build System
1> CMake does not need to re-run because C:/Users/Alex/Documents/helloworld/json/build/CMakeFiles/generate.stamp is up-to-date.
2>------ Build started: Project: json_unit, Configuration: Debug Win32 ------
2> Building Custom Rule C:/Users/Alex/Documents/helloworld/json/CMakeLists.txt
2> CMake does not need to re-run because C:\Users\Alex\Documents\helloworld\json\build\CMakeFiles\generate.stamp is up-to-date.
2> unit.cpp
2>C:\Users\Alex\Documents\helloworld\json\src\json.hpp(2358): error C2061: syntax error: identifier 'value_type'
View clang-win32
[15:26:45] <aknight> kkoehne: so are you working on clang-win32 support?
[15:38:32] <kkoehne> aknight: Nope
[15:38:49] <aknight> kkoehne: who is then? :-)
[15:39:00] <kkoehne> aknight: You? :)
[15:39:10] <kkoehne> aknight: I intend(ed) to
[15:39:34] <kkoehne> aknight: But haven't really come around to play with it much more than trying to compile qtbase, only to see it choking on the very first .cpp file
[15:39:44] <aknight> kkoehne: i've played around with it, but per lars' email i assumed someone was actually spending time/money on it
[15:39:45] <kkoehne> aknight: But I heard you had a patch somewhere to overcome this ...
[15:40:45] <aknight> kkoehne: i haven't touched it in a while, but there's a wip on my dashboard
[15:40:53] <lars> aknight: no currently, this is only my wishful thinking... ;-)
You can’t perform that action at this time.