Re: Use xenodm like startx?

2019-01-31 Thread John Ankarström
trondd  wrote:
> It's not really that complicated.  The bare minimum is to copy your
> .xinitrc to .xsession and then just run xenodm on demand with doas.  All
> the configs already exist in /etc/X11/xenodm.  Nothing requires you to run
> it at startup.
> 
> Here's what I've done:
> Copy your .xinitrc to .xsession
> 
> Copy (or modify in place) /etc/X11/xenodm/xenodm-config to $HOME
> 
> Edit xenodm-config and add
> DisplayManager*autoLogin:  yourusername
> 
> Comment out the call to Xsetup so you don't get the xconsole window
> !DisplayManager._0.setup: /etc/X11/xenodm/Xsetup_0
> 
> Then you can alias it to run it on demand.  Alias to startx if you want.
> alias xenodm='doas xenodm -config /home/myusername/xenodm-config'

Hm.  Thank you.  This works, except the environment in which I run xenodm is 
lost.  For example, I have ENV=~/.kshrc in my ~/.profile, but this isn't 
inherited to X11 ... I guess I should add these things to my .xsession, but 
then I'll have it in two places instead of once.

> Only thing I never figured out is how to make X and xenodm shutdown when I
> exit my window manager.

This too makes me feel like xenodm is far too complex for what I want.



Use xenodm like startx?

2019-01-30 Thread John Ankarström
Hi,

I just got OpenBSD installed on my new laptop, and so far, it works great. But 
since I applied the latest X11 patch, I can no longer use startx to launch X11, 
unless I do it as root, which probably isn’t a good idea. Seems like I have to 
use xenodm.

The thing is, xenodm is so complicated in comparison to a simple .xinitrc + 
startx. There are so many files I need to set up that I hardly know where to 
begin.

I don’t want a login screen, I don’t want X11 to launch at startup. I just want 
to start X manually from a simple .xinitrc. Surely I can’t be alone.

Any ideas or tips?

Best regards
John



Re: Missing libraries after upgrade to 6.4

2018-12-21 Thread John Ankarström

Juan Francisco Cantero Hurtado wrote:

$ rm -rf /usr/ports/{pobj,packages,plist}
$ pkg_delete strawberry
$ pkg_add -u
$ pkg_delete -a
$ cd /usr/ports/audio/strawberry
$ make install


Thank you!  That did it!



Re: Missing libraries after upgrade to 6.4

2018-12-20 Thread John Ankarström

Tom Smyth wrote:

Hello John,


Hi!


do you have PKG_PATH Variable set to  an old version ?
eg
export PKG_PATH=https://fastly.cdn.openbsd.org/pub/OpenBSD/$(6.3/packages/amd64/

export PKG_PATH=https://fastly.cdn.openbsd.org/pub/OpenBSD/$(uname
-r)/packages/$(uname -p)/

you can remove the PKG_PATH  variable as installurl now helps
find the correct packages from your favourite mirror


and simply populate /etc/installurl
with the url of your favourite mirror,
man installurl for more details


Unfortunately, I already use /etc/installurl (with 
https://cdn.openbsd.org/pub/OpenBSD) and have $PKG_PATH unset.


Best regards,
John



Missing libraries after upgrade to 6.4

2018-12-20 Thread John Ankarström

Hello all,

I have this port [1] that installed fine on 6.3, but after I upgraded to 
6.4, following the FAQ, I'm getting weird errors.


When running make install, it fails because qtbase-5.9.4 can't be 
installed, which is weird that it wants to do, because the version in 
ports is 5.9.6p1.  Here's the output: http://sprunge.us/z6d97h


When I try to run make rebuild, it complains about missing libraries for 
Qt5 stuff: http://sprunge.us/oEDaKE


Some proof that I've actually upgraded:

$ uname -a
OpenBSD lbsd.home 6.4 GENERIC.MP#364 amd64

$ cd /usr/ports; cvs status Makefile
[...]
Sticky Tag:  OPENBSD_6_4 (branch: 1.77.2)
[...]

Anybody got any idea as to what's going on?

Best regards,
John

[1]: 
https://files.jkvinge.net/packages/strawberry/strawberry-openbsd-port.tar.gz




Re: phonetic alphabet on OpenBSD

2018-10-15 Thread John Ankarström

Jan Stary wrote:

Are there any phoneticians running on OpenBSD?
How do you type the phonetic alphabet in vim?
Is there a standard keyboard layout for the English part of IPA?


It wouldn't be too difficult to create one.  I found this on DuckDuckGo 
via the search query "ipa xkb layout":


http://www.ajmakkas.com/pages/c_xkbipa.html

You could add that to /usr/X11R6/share/X11/xkb/symbols/ and use 
setxkbmap to switch to it.  I would assign a key binding to it in my 
window manager.


If you use a desktop environment like GNOME, you might want to edit 
../rules/evdev.xml in order to be able to find the keyboard layout in 
the graphical keyboard preferences.


Here's another good resource on X11 keyboard layouts in general:

http://people.uleth.ca/~daniel.odonnell/Blog/custom-keyboard-in-linuxx11

Best regards,
John



Re: ksh equivalent to shell-expand-line

2018-10-10 Thread John Ankarström

Hajime Edakawa wrote:

Hello Mr. Ankarström,

I have challenged to try to make shell_expand_line in ksh.
You can check it if you type M-C-e.


That sounds fabulous!  Thank you for your initiative!  The code looks 
interesting.



To be honest, I'm not sure if this is correct.
I only like OpenBSD, That's why I'm so sorry if they're wrong


It might be interesting to take a look at the source of mksh[1], another 
ksh implementation, which has a similar binding called evaluate-region.


[1]: https://www.mirbsd.org/mksh.htm

Best regards,
John



Re: ksh equivalent to shell-expand-line

2018-10-07 Thread John Ankarström

Klemens Nanni wrote:

On Sun, Oct 07, 2018 at 07:30:15PM +0200, Tomasz Rola wrote:

Another trick may be executing the line with echo prepended - should
do all expansions and write what will be executed. I think it is not
going to work too well if for loop is being echoed, and other such
things, so perhaps quoting a command and echoing would do the job.

This will break any non-trivial construct including pipes, command lists,
loops, (nested) quoting, et al.



To which message is this a response?  It seems I haven't received it, 
but I'd like to read it.  Tomasz?


Best regards,
John



Re: ksh equivalent to shell-expand-line

2018-10-07 Thread John Ankarström

Klemens Nanni wrote:

On Sat, Oct 06, 2018 at 09:38:42PM +0200, John Ankarström wrote:

Is there a way for ksh to expand a $(command substitution) without having to
execute the entire line?

No.


That's too bad.


bash provides this via shell-expand-line (bound to Ctrl-Alt-e by default),

 From bash(1):

shell-expand-line (M-C-e)
Expand the line as the shell does.  This performs alias and
history expansion as well as all of the shell word expansions.

And yet, it disregards quoting and will errornously expand the following
example into multiple words instead of one:

bash-4.4$ echo "$(echo a b)"
bash-4.4$ echo a b


There is a discussion about this behavior on the bug-bash mailing list:

https://lists.gnu.org/archive/html/bug-bash/2016-11/msg00010.html

Turns out to be a relatively simple fix, but the old behavior will 
remain the default (as of 2016).



and ksh seems to have expand-file, but that only works for filenames.

We have no other expanding functions.


Would there be any interest among the pdksh developers in a function 
like shell-expand-line (but which works properly), if somebody like me 
did the work?


Best regards,
John



ksh equivalent to shell-expand-line

2018-10-06 Thread John Ankarström

Hello again,

Is there a way for ksh to expand a $(command substitution) without 
having to execute the entire line?


bash provides this via shell-expand-line (bound to Ctrl-Alt-e by 
default), and ksh seems to have expand-file, but that only works for 
filenames.


Any ideas?

Best regards,
John



x, c and v misbehaving in GTK applications

2018-09-27 Thread John Ankarström

Hello all!

I'm having this weird issue on OpenBSD 6.3.  In some GTK applications -- 
so far only in Evolution and Chromium, but not Firefox or SeaMonkey -- 
the letters x, c and v have stopped working in some text fields. 
Instead of entering the letters, it's as if Control is pressed and they 
perform Cut, Copy and Paste.


Has anybody experienced anything similar?  Any idea what the problem 
might be?


I'm fairly new to OpenBSD and its mailing lists.  Is this the 
appropriate place to discuss this, or should I report the bug somewhere 
else?  If so, where?


Much thanks,

John