hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar-group.org | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | This channel is logged: irclog.cct.lsu.edu
diehlpk_work has quit [Ping timeout: 240 seconds]
K-ballo has quit [Quit: K-ballo]
hkaiser has quit [Quit: Bye!]
K-ballo has joined #ste||ar
K-ballo has quit [Quit: K-ballo]
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
<dkaratza[m]>
Is there a way to automatically set the max length line of a code file? I dont wont my editor to do it only for me (change the view). I want to add a break line if the length of line is larger that a specific no
<K-ballo>
automatically no, but clang-format will impose a limit (at least for hpx's clang-format config
<dkaratza[m]>
K-ballo: so, do i need to fix this or is it fixed automatically?
<K-ballo>
if you are writing hpx code, you are expected to clang-format it when you submit a PR
<dkaratza[m]>
K-ballo: im writing docs so i dont know if that also applies there
<K-ballo>
docs in code files?
<dkaratza[m]>
no, rst file
<K-ballo>
so not a code file then
<K-ballo>
your text editor of choice will likely have a similar auto formatting capability
<K-ballo>
unless it's vi
<dkaratza[m]>
yeah but the only thing i can do with my editor is change how I see it. I dont want to wrap the text because that won't change the file itself. so when i push the lines will be long. i just want to break the lines
<K-ballo>
you want to look for auto formatting capabilities, not presentation settings
<K-ballo>
something that runs and reshapes your text to follow formatting options
hkaiser has quit [Ping timeout: 240 seconds]
hkaiser has joined #ste||ar
RostamLog_ has joined #ste||ar
RostamLog has quit [Ping timeout: 250 seconds]
RostamLog has joined #ste||ar
diehlpk_work has joined #ste||ar
<gonidelis[m]>
dkaratza: maybe just split screen and let it wrap up in hlaf your screen ;p ?
<hkaiser>
dkaratza[m]: what editor do you use?
<hkaiser>
usually there is a command called 'reflow' or 'rewrap'
<dkaratza[m]>
<hkaiser> "usually there is a command..." <- I have vscode
<gonidelis[m]>
K-ballo: so you basically mean that they refactor and repropose sth else for 23? i think the dl is over for that?
<K-ballo>
no, that's not what I mean
<ms[m]>
gonidelis: I think with that vote there's a near 0% chance of having any part of p2300 in 23, but it'll still be targeted for 26
<gonidelis[m]>
K-ballo: what did you mean?
<gonidelis[m]>
ms: ya exactly
<hkaiser>
I know there was a discussion to reduce the scope of p2300, not sure if that will happen
<K-ballo>
no consensus for aproval != reject
<K-ballo>
rejection requires consensus too
<gonidelis[m]>
K-ballo: wasn't aware of that detail. but yeah, that's still better than rejected. nevertheless no standardization for the next 3-4 years means people will go around like zombies looking for custom implementations (HPX)
<gonidelis[m]>
sounds both good and bad
<K-ballo>
people who actually care would already be using and continue to use custom implementations for years until 23 settles, what's 3 more years?
<gonidelis[m]>
K-ballo: next standardizatoin cycle
<gonidelis[m]>
were you in favor btw? as were?
<K-ballo>
"what's 3 more years?" -> what difference do 3 more years do, for something they are already doing and will have to continue doing at least for some time past C++23 approval
<gonidelis[m]>
s/?/./
<K-ballo>
instead of switching to std:: sometime in the next 8 years they'll be doing it in 11 years
<gonidelis[m]>
true. but it is my impression that organizations and companies tend to rely on standardization. that said, people might be scared off until then which mean less users, less issues, slower development?
<gonidelis[m]>
i don't kno i am just a master's student. just speculating
<gonidelis[m]>
this line throwing me a `sed: -e expression #1, char 7: unterminated `s' command`, I ll be damned
<gonidelis[m]>
anyone has a clue bout sed peculiarities?
<hkaiser>
'#' is sed's comment character
<gonidelis[m]>
ahh ok...?
<hkaiser>
the command you linked extracts the version numbers from the CMakeLists.txt
<hkaiser>
here \1 is substituted with whatever was matched inside the first pair of \(\)
<gonidelis[m]>
hkaiser: so `VERSION_MAJOR=$(sed -n 's/set(HPX_VERSION_MAJOR \(.*\))/\1/p' CMakeLists.txt)` and then `echo $VERSION_MAJOR` should give me sth like "1"
<gonidelis[m]>
well this cmakelists and the .sh files are in the same path
<gonidelis[m]>
ah... exactly what i though
<hkaiser>
it will use the one it sees in the current directory
<gonidelis[m]>
i reckon i should move the .sh on top then
<hkaiser>
or do a ./tools/script.sh
aacirino has quit [Ping timeout: 240 seconds]
<gonidelis[m]>
...................
<gonidelis[m]>
why is the answer always so simple
<gonidelis[m]>
any tool suggestions for saving every package installed and files somehow compactly in order to reinstall my Linux (ubuntu)? I have a mega driver issue