Am 2019-06-07 15:21, schrieb ilf:
Jochen Sprickerhof:
Up to dwm 6.1, the status bar text had a padding space on the very
left edge. In 6.2, that's not there any more. Even if specifically
adding one or more space glyphs to the text passed to "xsetroot
-name", these are stipped.
Should be this
Am 2018-03-11 01:48, schrieb Sergey Matveev:
*** Markus Teich [2018-03-10 17:09]:
I don't know crypto_argon2i. I'd use the standardized HKDF2 scheme to
derive
the key.
HKDF algorithm is not aimed to be used with passwords. It is ok to be
used with Diffie-Hellman outputs for example
Am 2018-03-11 04:21, schrieb Anselm Garbe:
On 10 March 2018 at 06:08, Markus Teich
wrote:
Should be fine, but the salt should not be secret (you need to sync it
between devices where you want to use this system after all). The
point is
that you can give your encrypted database as it is stored
(1)
Setup:
- Generate a random salt and store somewhere safe.
Note that it should not be required to keep the salt secret.
Encryption:
- Read the salt from its location and the master password from the
console. Use those to generate a key with crypto_argon2i.
I don't know crypto_argon2i. I'd
Am 2018-03-08 18:47, schrieb pet...@riseup.net:
Looking at the chacha API one needs to use a nonce, in the monocypher
implementation it is 24 bits wide, which would give the option of
almost
17M runs with a single key. IIUC adding a salt would further randomize
the output and possibly prevent s
pet...@riseup.net wrote:
I have to yet read up if it is safe to use
with a single key, i.e. encrypting n passwords with the same secret
key.
Make sure to use salting in this case. Otherwise using the same password
for multiple sites/keys would be visible.
You also want to hide the keys them
Thomas Levine wrote:
> I settled on the following mpv configuration.
> https://thomaslevine.com/scm/langrompiloj/artifact/6a086022d93af1a1
> https://thomaslevine.com/scm/langrompiloj/artifact/161b62d352fec4f7
>
> This produces a file like the one below, which I edit until the subtitles are
> accep
Heyho,
Hiltjo Posthuma wrote:
> Minor nitpick, I'd prefer a space after the wildcard:
> > + snprintf(msg, sizeof(msg), "* %s %s", nick,
> > &buf[3]);
I think that looks weird. No actual research, but I think I've seen the format
without a space more often and the `*` is
Heyho,
I am happy to announce the version 1 release of sent. It was already released a
few days ago, I just forgot the announcement. Sorry, all you hungry package
maintainers. The release numbering has been changed to only single numbers, so
the next releases will be 2, 3, and so on.
Notable chan
Hiltjo Posthuma wrote:
> Some directories indeed did not have a checksums file (it didn't have these
> before either).
The script generating the .tar.gz archives and checksums does not yet copy them
to the dl.suckless.org hierarchy. We might want to remove the subdirectories
(like tools/) level on
Mattias Andrée wrote:
> * An alternative to signature files is to sign the tags in Git, and those
> that care enough could pull releases from git instead.
That is a nice idea. It doesn't require any extra signature/checksum file cruft
on the webserver. It can easily be made optional and is in th
Mattias Andrée wrote:
> If the server's authenticity can be proven with HTTPS,
> what additional secure does PGP-signatures provide?
Some people trust persons they know more than they trust random corporations
with questionable security policies. Other people think PGP sucks. I don't know
which gr
Hiltjo Posthuma wrote:
> Checksums are available in each project directory, yesterday I've added
> SHA256 checksums.
>
> For example:
> SHA256: http://dl.suckless.org/dwm/sha256sums.txt
> SHA1: http://dl.suckless.org/dwm/sha1sums.txt
> MD5:http://dl.suckless.org/dwm/md5sums
Lennart Poeterring wrote:
> …
Greetings Lennart,
you seem to have misspelled your last name. Also, stop talking, send patches!
I wish you have the loveliest of days!
--Markus
Andrew Cobaugh wrote:
> Trying one more time to bisect this, I ended up at
> 04143fd68dbc656905714eff5c208fadb3464e25 as the commit that introduced
> the "slock: getpwuid: cannot retrieve shadow entry (make sure to suid
> or sgid slock)" error for my environment. This was with replacing
> HAVE_SHAD
Andrew Cobaugh wrote:
> I'm actually having a hard time bisecting, because even vanilla 1.3 fails to
> work correctly. The screen locks, but then it doesn't accept my password.
>
> There is this patch in the ports tree which is necessary to make 1.3 work for
> me, but it doesn't seem to apply clea
Heyho Andrew,
Andrew Cobaugh wrote:
> I believe this is related to this change:
>
>
> http://git.suckless.org/slock/commit/?id=04143fd68dbc656905714eff5c208fadb3464e25
Can you confirm this commit is the cause of the regression by using git bisect?
> In my case, my passwd field contains '*'
doug livesey wrote:
> Could you advise me on how to apply the patch to the st project? (Does it
> maybe need to be done in a broader context of a suckless project?) Oh, and I
> couldn't find any mention of resizehints in the code to set to false, so I
> think I've misunderstood there, too.
Heyho,
Greg Reagle wrote:
> If it were possible to get st to do the same thing, such a feature would
> probably not be included in the main repository due to the preference for
> small fast and simple that characterizes suckless programs.
Heyho,
I agree. The main point here is imho that dwm already has
doug livesey wrote:
> I shall have a play with that after work, thankyou!
Heyho,
I just noticed I did not update the patch on the website yet. I did this now, so
make sure to use the latest one[0], which is also simpler than the previous ones
and probably does not produce as many merge conflicts
Heyho doug,
doug livesey wrote:
> I'd have to figure out how to code that patch, first! :)
Nope, just use that[0] patch.
> However, everything I've tried so far hasn't enabled me to run st in
> full-screen mode, so it's looking like the window manager doesn't enable full
> screen without the app
hiro wrote:
> try with a small group of people first that actually has a need for privacy.
Heyho,
in the special case where this privacy is to be achieved not with encryption,
authentication and authorization (to limit the number of entities who are
allowed to learn the secret which should be pro
Patrick Bucher wrote:
> On Fri, Jan 13, 2017 at 11:23:28PM +0800, Ivan Tham wrote:
> > Windows key is a better choice most of the time since it's unused
> >
> As you and many others suggested, I am now using the Windows key as well. It's
> a bit strange at the beginning, for my thumb has to move a
Ian Remmler wrote:
> There's not much to see, really. I don't think a picture tells enough to
> justify adding to the repo. I'll likely flesh out the readme a bit. But it's
> easy to build and run to see what it does.
Heyho Ian,
I also think an image would be helpful but should not be added to th
Ricardo M. Vilchis wrote:
> slock: getgrnam nogroup: group entry not found
Heyho Ricardo,
then you (or even the fedora package maintainer of slock) should change the
value in config.h accordingly.
--Markus
Martin Kühne wrote:
> This reminds me, we're talking about i3 here.
Heyho,
if you're using unclutter, this thread[0] could also help you out. Either way it
seems that something else on your system already has an active keyboard/mouse
grab preventing slock from starting.
--Markus
0: http://list
Heyho,
I am happy to announce the release of slock version 1.4. slock is a simple X
display locker.
You can download it at: http://dl.suckless.org/tools/slock-1.4.tar.gz
The changes since version 1.3 are:
- fix CVE-2016-6866
- add proper priviledge dropping
- use explicit_bzero from OpenBSD to c
Martin Kühne wrote:
> TL;DR, while I'm sure most of this stuff holds further scrutiny, I just doubt
> it's generally a good idea to list so many problems while providing no
> technical context whatsoever.
Heyho Martin,
I didn't want to do the whole schoolwork for Lukáš, so I just gave a
hint/poss
lukáš Hozda wrote:
> Do you know about some bad things Apple has done in their pursuit of
> ever-increasing profits? Do you know about ways Apple is against free and
> open-source software? Please let me know. Naturally, if you know about some
> good deeds of Apple, I accept them as well.
Heyho Lu
Alexander Keller wrote:
> If the alternative is too much, perhaps changing
> strictssl = FALSE \* Refuse untrusted SSL connections *\
> to
> strictssl = FALSE \* Validate SSL certificates from server *\
> would help better inform what it does. My initial understanding when I
> used
pranomes...@gmail.com wrote:
> I can't be bothered with writing an own vi/vis/vim layout for the keyboard
> layout I use (neo2).
Heyho,
I also use the neo2 keyboard layout with vim for a few years now. I don't
understand why you would have to change the keybindings at all, since the
mapping of le
Christoph Lohmann wrote:
> I am stepping back from my maintainership and my role as an admin of
> suckless.
Heyho Christoph,
keep those global warming causers in check with whatever you are focusing on
now! ;)
On a more serious note:
Thanks for your work, especially on st (which showed me t
Martin Kühne wrote:
> On Tue, Sep 27, 2016 at 2:40 PM, FRIGN wrote:
> > however, "bioc" or "binoc" might be nice memorable names for the
>
> Why not carry the IRC back into the name and make it binoirc or even birco?
Heyho,
This is intended to be used with other chat protocols as well, so I wou
---
Jo dawg, I heard you like presentations so I put a presentation after your
presentation so you can have infinite presentations.
sent.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sent.c b/sent.c
index fc319be..8580d0a 100644
--- a/sent.c
+++ b/sent.c
@@ -437,7 +437,
u...@netbeisser.de wrote:
> do you know of a suckless linux debugger? what is an alternative to ptrace?
Heyho Stefan,
just use printf debugging.
--Markus
Anselm R Garbe wrote:
> I'm glad to announce the preliminary slcon3 schedule[0].
Heyho,
I'll arrive on friday around noon. If someone else wants to join early, we can
meet at the hotel lobby and work on some projects until the official welcome in
the evening.
--Markus
Kevin Michael Frick wrote:
> people keep sending me word documents :/
Heyho,
respond with a plain text document without file name extension and laugh
at their silly faces when they don't know how to open it.
--Markus
Joseph Graham wrote:
> I am accustomed to having scrolling and multiplexing (in > xfce4-terminal).
> To get these the suckless way should I:
> a. use tmux/screen
> b. use tabbed and the st scrollback patch
> c. something else
Heyho Joseph,
for local multiplexing I use tabbed, since its keybinding
FRIGN wrote:
> Even if you use self-signed certificates on your server, which provide 0
> guarantee that the server you are contacting really is the "right" one, it
> still means the traffic itself is encrypted, with all benefits of it.
Heyho,
In our case it would do nothing. There is no "secret"
Paul Menzel wrote:
> I noticed, that it’s currently not possible to securely browse the Web site
> [1].
>
> Are there plans to allow access using HTTP over SSL?
Heyho,
I'd also like that. My main argument is that it helps against MitM attacks when
our precious software is downloaded. However I'm
Paul Menzel wrote:
> If I am not mistaken, this is really a corner case. The user has to set
> `actionfps` to zero in `config.def.h`.
>
> ```
> config.def.h:static unsigned int actionfps = 30;
> ```
Heyho Paul,
maybe you can make your compiler happy by making the variable const? It should
then
Eric Pruitt wrote:
> @@ -944,40 +944,36 @@ void
> grabbuttons(Client *c, int focused)
> {
> updatenumlockmask();
> - {
> - unsigned int i, j;
> - unsigned int modifiers[] = { 0, LockMask, numlockmask,
> numlockmask|LockMask };
> …
> + unsigned int i, j;
> +
Anselm R Garbe wrote:
> I'm not sure if this feature is really required. Typing a wrong password can
> be corrected on second attempt anyways.
>
> What is the opinion of other users to this change?
Heyho,
I also don't think adding this patch to mainline is neccessary. You can still
put it on the
Marc Collin wrote:
> Original sup by pancake is copyleft. (loose term, could be many things)
> Jaromil's sup (which is based on pancake's) is LGPLv3.
Heyho,
ISC or MIT should be compatible with LGPL, so I think it's fine to pull the
fixes if we relicense sup under one of those.
--Markus
Eric Pruitt wrote:
> I think you should add another color option to the configuration.
Heyho,
if you add that to the patch be sure to also run `sed -i s/slock/nyanlock/` on
all files before submitting the new version.
--Markus
Heyho,
seeing the new subject I feel obligated to leave this link here:
https://www.destroyallsoftware.com/talks/wat
--Markus
David Phillips wrote:
> This /may/ not achieve quite the behaviour that Frostyfrog is after. By
> example, I would appreciate if slock was able to only show failcolor when the
> buffer is empty and a key which actually modifies the buffer was pressed.
Heyho David,
we already discussed this. There
Frostyfrog wrote:
> So, I understand that the red background color is supposed to signify that
> someone tried to log into the machine, but does it really need to turn the
> screen red when I press a no-op key?
Heyho,
Just set failonclear to false in config.h.
--Markus
Heyho,
Rashad Kanavath wrote:
> How do i configure dwm to have tabbed + st for default terminal window?
>
> currently when I do Ctrl+Shift+Enter I have an st terminal. I want to
> have it inside a tabbed.
I use this:
static const char *termcmd[] = {"tabbed", "-c", "-r", "2", "st", "-w", "''",
N
hiro wrote:
> Anyway, it would be more useful to concentrate on the password checking part,
> it segfaults commonly (which is fucking ridiculous!!) because ldap, linux,
> etc. suck.
Heyho hiro,
Same argument as for surf applies here: If you can't fix the suckyness, you have
to build a nice interf
Martin Kühne wrote:
> stdout could print an api secret "[locked]" and the calling script could act
> upon that.
>
> slock | {
> read
> if [[ "$REPLY" = "[locked]" ]]; then
> suspend
> else
> yell at user or power off for added security
> fi
> }
Heyho Martin,
thats basically the
hiro wrote:
> How does your integrated execution of s2ram change that? Your slock can still
> fail in just the same way.
Heyho hiro,
with the patch first the cover window is created and the keyboard and mouse are
grabbed. I consider this setup. If it fails, slock exits and does *not* execute
s2r
hiro wrote:
> - new: slock now allows to run any command after the screen has been
> locked, for
>example suspending to ram.
>
> how come you can't just run slock from a shell script instead?
Heyho hiro,
you don't know when the screen is locked, since slock does not fork itself. If
you want
Heyho,
I am happy to announce the release of slock version 1.3. slock is a simple X
display locker.
You can download it at: http://dl.suckless.org/tools/slock-1.3.tar.gz
The changes since version 1.2 are:
- bugfix: The cover window now resizes correctly when new screens are added or
the resolu
Anselm R Garbe wrote:
> Fine by me, don't forget to update config.mk and LICENSE as well with 1.3
> version info and copyright update.
Heyho,
I think its ready to ship, even added a man page. Is anything missing? If not,
feel free to tag and create the release tar.gz. I already pushed the updated
Heyho,
I propose to tag a new v1.3 release for slock. I have no open patches or bug
reports on my list and my attention was brought to it a few times already. A
major thing noted by most people was the fix for resizing the cover window on
xrandr resize events (f5ef1b8), which can be considered a s
Louis Santillan wrote:
> One of the things I don't like about the Chrome (and specifically v8)
> codebase is how google-centric the build process is. By that I mean the
> build basically assumes you're a googler with dozens of cores and TBs of
> RAM and infrastructure to throw at the build pro
Marc André Tanner wrote:
> The END-mapping was actually using text_line_lastchar not text_line_end. I
> now added a new key action for text_line_end. The behaviour might still be
> inconsistent (for example in vim's visual modes `$` seems to behave like
> ) but at least it can now be configured vi
Nick wrote:
> I had forgotten about this until today, but the above fix still hasn't been
> applied to the Makefile, and I think it should be.
Heyho Nick,
sorry for the delay. I decided to add the hint to the error message on failing
to disable the OOM killer instead of the Makefile. Should be up
Brad Luther wrote:
> Say somebody manages to "clamp" any letter or number key without you noticing,
> and you for the better of it cannot type in your password (not because it's
> all-caps, but because it's spamming lots of chars).
>
> So we want the screen to turn red on key down? Any key? Why ju
FRIGN wrote:
> So we want the screen to turn red on key down.
Heyho,
another even more annoying example is: I actually type my password so fast, the
key release events are sometimes in the wrong order. You can test it with xev,
just type some text as fast as you can and you will find something li
David Phillips wrote:
> Previously, if failonclear was set to True and a modifier key (especially
> shift) was pressed and held in order to modify the next keypress, slock would
> detect that a keypress had been made, observe that the buffer was clear and
> set the screen to the failure colour.
>
Brad Luther wrote:
> But if the behavior for Markus is different, then his slock is bugged :)
Heyho Brad,
nope, I just have the failonclear set to false in config.h. Then the empty input
state only turns red after a failed attempt. Otherwise it always is red except
right after starting slock. And
Brad Luther wrote:
> If you're typing your password and gets a char wrong, you go and delete the
> char, then continue to type the pass and 'enter' to unlock the screen. All
> good, screen is blue all the time. Unless... you get the first char wrong. If
> you mistype the first char of your passwor
David Phillips wrote:
> On Thu, Jan 14, 2016 at 09:47:37AM +, Dimitris Papastamos wrote:
> > On Thu, Jan 14, 2016 at 09:02:43PM +1300, David Phillips wrote:
> > > diff --git a/sent.c b/sent.c
> > > index fc5e389..88abe90 100644
> > > --- a/sent.c
> > > +++ b/sent.c
> > > @@ -153,7 +153,7 @@ fil
Heyho Marc,
something I don't seem to be able to figure out: When pressing the END key in
insert mode, in vim the cursor moves after the last regular character in the
current line, basically over the newline character, if you choose to display it.
In vis however it does only move to the last regul
Heyho Marc,
Marc André Tanner wrote:
> > I don't know the best way to fix it, but it would
> > be possible to strip the newline from within the `cmd_set` function.
>
> I have taken this route for now. Should be fixed?
Yep, works.
> > Ah right, I see it's used for `~` now. Could you add this map
Andreas Doll wrote:
> On 2016-01-15 at 23:21, Markus Teich wrote:
> > I don't like the man-page approach. Documentation always looses
> > synchronization to the codebase, so my proposal would be to output a similar
> > error message in slock. The link from "sl
Heyho Jan,
Jan Christoph Ebersbach wrote:
> - Setting defaults requires patching some c file instead of config.def.h
have you tried the visrc.lua file in the repository root? You can do any `set`
command in there for your defaults. See my other mails in this thread.
> - It took me ages to start
Brad Luther wrote:
> On the geometry being a multiple of the font, you say that "In the
> past there was some work to avoid this situation adding pagging pixel
> lines, and it generated a lot of problems". But ACE said there's still
> a way touse it like that, by setting resizehints = False in conf
Marc André Tanner wrote:
> > Maybe a global default 'syntax highlighter' applied regardless of file type
> > could do the job?
>
> Maybe, yes. However you probably want these features in combination with
> regular syntax highlighting. Maybe a layered approach would somehow work
Thats what I meant
Heyho Marc,
Marc André Tanner wrote:
> On Sat, Jan 16, 2016 at 07:09:26PM +0100, Markus Teich wrote:
> > - Why did you choose to use full black instead of the base03 color from
> > solarized?
> >
> > - Even after "fixing" the above the colors don't l
Marc André Tanner wrote:
> Did you (or anyone else) try it? First impressions? Which features did you
> miss the most?
Heyho Marc,
I built the standalone version and tried some stuff. I also went through my
vimrc to find any features I would like to use. Here are my comments in no
particular orde
Andreas Doll wrote:
> By the way, xscreensaver successfully locks the screen, and prints
>
> couldn't grab pointer! (AlreadyGrabbed)
>
> and displays the verification window only upon keyboard activity. Without
> unlcutter this window appears also on mouse input.
Heyho Andreas,
This is probably
Andreas Doll wrote:
> I've just tested with i3lock 2.6 (on Debian stable), which also returns after
> a short moment to the desktop without verification, complaining
>
> $ i3lock
> i3lock: Cannot grab pointer/keyboard
Heyho Andreas,
I assume this is the same issue for slock. From XGrabKeyboard(3
Andreas Doll wrote:
> I've tested with slock 1.1 and 1.2. Upon researching this issue I found that
> it was already noticed by others. Arch wiki [1] blames unclutter for this and
> notes that is also breaks i3lock, which isn't confirmed in [2].
>
> I'm not sure if you are fine with the current beh
FRIGN wrote:
> I had that floating in my mind as well, but the thing is, that some utils call
> usage() pretty often. You would have to specify the long usage-string every
> time which makes it unfeasable.
Heyho FRIGN,
yeah right…
$ grep -r "usage()" | wc -l
219
$ ls *.c | wc -l
87
I thought a
FRIGN wrote:
> I thought about this tonight and came to the conclusion that this "hack"
> doesn't introduce too many problems.
Heyho FRIGN,
what do you think about making `usage(int status, char *shortargs)` an
eprintf-like function in eprintf.c? This might clear things up for everyone.
--Markus
e...@bestmx.net wrote:
> http://file.bestmx.net/ee/suckless/
Heyho,
you have a line with just an indentation tab in eprintf and enprintf.
Also why upload it instead of just sending the patch via mail?
--Markus
e...@bestmx.net wrote:
> how about "age" and "size" attributes too,
> just to ensure age and size "equalities".
Heyho,
I am looking forward to 1% commits adding the word "mum" or "dad" in random
places. How do you plan to check if all the SLoC are evenly distributed between
the different attribut
Heyho,
Martin Ueding wrote:
> I think I did not mention properly that the external screen is additional to
> the laptop screen. slock would have to create a second window to cover both
> displays.
I don't remember if I tested with automatically adding another screen while
locked. Let me know, whe
FRIGN wrote:
> usually, slock should get a XRRScreenChangeNotifyEvent when the screen size
> changes. I wonder why it isn't fired; maybe there's a bug in slock or in
> awesome wm not sending proper events.
Heyho,
this should be fixed since January. Martin, can you confirm the bug persists
when us
David Kennedy wrote:
> However, this new function still needs to know three things:
>
> 1. The font to use
> 2. The text to be rendered
> 3. The length in bytes of the utf8 encoded string
>
> No. 2 is easy. No. 1 and 3 are all tangled up in drw_text. So, before calls to
> drw_text and TEXTW can b
Heyho,
I am happy to announce the version 0.2 release of sent. This is just a bugfix
release to help package maintainers before the migration to farbfeld is done for
version 0.3.
http://tools.suckless.org/sent
http://git.suckless.org/sent
http://dl.suckless.org/tools/sent-0.2.tar.gz
--Markus
Heyho,
a little annoyance, that bugged me for quite a while is that you get a short
white "flash" when changing between different tabbed clients running surf. This
is mostly only visible when both websites have a dark background. I tested it
and I can "fix" it for these cases with the following li
Heyho,
Claudio wrote:
> I've implemented a web-based "port" of sent called wsent. I agree to not
> use the web for anything so I decided to abandon the project after reading
> the Quenting Rameau post where he suggests a slide to image conversion.
> Though, since I've put some effort on writing w
hiro wrote:
> I have done some presentations in word, fixing errors that i did in the night
> before while still presenting. people *love* the instant gratification of
> having their contribution incorporated into the "slide" in the most visible
> way.
Heyho hiro,
you're welcome to provide a patc
Joerg Jung wrote:
> However, can you tag/roll a new release/tarball please?
Heyho Joerg,
I plan to make a 0.2 bugfix release before merging the farbfeld change. However
I would like to wait a few days before that to see if you guys find some more
bugs. ;)
--Markus
Qentin Rameau wrote:
> > > > 'sent empty' with empty being a 0-length file will produce a
> > > > memory access error.
>
> I think I was able to fix that, please try the recent patch I posted on
> hackers@.
Heyho,
Yeah, sorry, I forgot to commit and push my fix, but now it should really be
fine,
Joerg Jung wrote:
> Have you compiled sent with address sanitizer as suggested in the link, or
> enabled the malloc.conf J option on OpenBSD, as mentioned above?
Heyho Joerg,
sorry, I missed that point. Please check again, I just pushed a fix, which
should work. I could not test it, since I don't
Marc Collin wrote:
> Is there any way to export the 'sent' presentation in case I need to use it on
> another machine that doesn't have 'sent' installed, but supports .png ?
Heyho Marc,
no such feature is planned. If you look at e.g. Powerpoint you also need the
application installed. For latex-b
Joerg Jung wrote:
> Here comes another one...
>
> As mentioned in this thread:
> http://marc.info/?t=14477246942&r=1&w=2 in this mail:
> http://marc.info/?l=oss-security&m=144774881126397&w=2
>
> 'sent empty' with empty being a 0-length file will produce a memory
> access error. On OpenBSD w
u...@netbeisser.de wrote:
> On Tue, Nov 17, 2015 at 01:34:30AM +0300, ret set wrote:
> > Segmentation fault
> > ~/src/sent-0.1$
>
> different crash with zzuf:
>
> zzuf -r 0.06 ./sent sent.c
> …
> error, cannot load font: 'ubuntu:size=10'
> error, cannot load font: 'roboto:size=10'
> error, cannot
FRIGN wrote:
> A better way, as I suggested at hackers@, would be to find a way to ad-hoc
> convert png's, gif's, whatever, to farbfeld. This would simplify the
> sent-code dramatically and also actually bring the benefits of the farbfeld
> format.
Heyho ACE,
as explained in further detail this
Greg Reagle wrote:
> There are indeed some people on this list who interpret plain bug reports as
> rude and react in a hostile manner to them, even though
> http://suckless.org/community says that dev@ is appropriate for bug reports.
> I wish these people would adjust their attitude. Not only are
Jan Christoph Ebersbach wrote:
> Since Space is very common in other presentation tools to advance to the next
> slide it would be a great default for sent as well. The attached patch adds
> the Space key as another way to advance to the next slide.
Heyho Jan,
merged. Thanks for the contribution
KIMURA Masaru wrote:
> > ... takahashi style presentations ...
>
> you might also check monta method?
Heyho,
Interesting. Just set the first font to something like `dejavu sans mono` then
you can duplicate the slides where you want to apply the monta method and use
`_` as a placeholder for the c
Heyho,
v4hn wrote:
> > and what you think was causing it.
>
> On Tue, Nov 17, 2015 at 01:34:30AM +0300, ret set wrote:
> >> Subject: [dev] sent-0.1 or libxft bug
> >> [...]
> >> Program received signal SIGSEGV, Segmentation fault.
> >> 0x77529980 in XftCharExists () from
> >> /usr/lib/x8
Nick wrote:
> But regardless, as far as I can see this is fixed in the latest code
> in git, aa713a8a342ec0e6eca173cd4489834f8baa0a86.
Heyho,
Yes indeed, it was the same segfault mentioned earlier. I replied to both of
them, but probably your MUA does not show my reply in both threads in threadi
Heyho,
ret set wrote:
> $ make && ./sent <(python -c 'print "A\n"*4000')
> …
> Segmentation fault
Stephen Whitmore wrote:
> When running the example presentation, I hit a segfault when I reached the
> first slide with an image (@nyan.png). See attached for backtrace. This only
> seems to happen
1 - 100 of 451 matches
Mail list logo
