Hi,
I'm watching your projects since a couple of months. Today I tried to
update st (i replaced the less important parts with (...) and added two
blank lines before each prompt for readability):
[0][st] (master) - git remote update
(...)
[0][st] (master) - git merge origin/master
Hi
On Mon, Nov 25, 2013 at 4:32 PM, Matthias Beyer m...@beyermatthias.de wrote:
Hi,
I'm watching your projects since a couple of months. Today I tried to
update st (i replaced the less important parts with (...) and added two
blank lines before each prompt for readability):
[0][st]
On Mon, Nov 25, 2013 at 04:32:28PM +0100, Matthias Beyer wrote:
Hi,
I'm watching your projects since a couple of months.
From the rest of the email it seems like you not only watched it, but
also used st.
Today I tried to update st (i replaced the less important parts with
(...) and
Hello
On 11/25/13, Silvan Jegen s.je...@gmail.com wrote:
Hi
You have to make sure that the config.h you are using actually matches
the checked-out version of st.c (i. e. checkout config.def.h and copy
it to config.h for the default settings).
to add to this, bellvolume is declared in
You guys were right, I did not copy the config.def.h file to config.h!
--- snip ---
On 25-11-2013 16:59:08, Alexander Huemer wrote:
Is '[0][st] (master) -' your shell prompt? That's highly unlikely.
It is! I use xterm (I know, shame on me) and I'm just watching the
repo, not using the
On 2013-11-25 19:51:33 +0100, Matthias Beyer wrote:
Yes, I understood what they mean, but I thought I did not make any
modifications in config.h,... but seemingly I did,... that's what got
me!
It's not just about whether you make changes to config.h, but also about
the fact that config.h can
On 2013-11-25 10:59:10 -0500, Carlos Torres wrote:
so this all gets fixed if you merge in updates to config.def.h into
your config.h.
My recommendation if you are using two upstreams with git is to symlink
config.h to config.def.h, and then just merge the one file.
(although, there are like a
