antiX Screenshots

[asqwerth]

I'm back in MX17.

Used the pkill command and then ran the conky. Got this message:

Code: Select all

tuaz@mx17final:~
$ conky -c "/home/tuaz/.conkyrc" &
[1] 6178
tuaz@mx17final:~
$ conky: Syntax error (/home/tuaz/.conkyrc:2: unexpected symbol near '#') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:138: unexpected symbol near '}'

[1]+  Exit 1                  conky -c "/home/tuaz/.conkyrc"

But looking at the conky for grimy clock, line 151 is a blank line, while lines 152 to 155 are:

Code: Select all

# -- Lua load -- #
#lua_load /media/5/Conky/easysid/MechClock/fancyclock.lua
lua_load /home/tuaz/LUA/fancyclock.lua
lua_draw_hook_pre main

The path for my lua script location is correct. Is there some issue with using capital letters for the folder path?

Line 138 is commented out so again I don't understand the error message:

Code: Select all

## ${lua conky_draw_bg 10 0 0 0 0 0x000000 0.2}

Still can't run it. So weird.

[male]

I made another picture for a better explanation.

I use the Terminator, because it can be divided so well visible
Left 1.9 Right 1.10 / MX17 - daily updated

- the pkill command is specified above with full path in quotation marks

- below is the start command. If the configuration to be executed is in the user's $HOME, the full path need not be specified. No quotation marks!

Both commands need the AND character & at the end, so that the terminal / process is released again.

MX17 is equipped with the Conky-Syntax 1.10. The configuration is written in Lua. Conky 1.9 however not
That's why "Conky-Syntax 1.10" of MX criticizes the character '#' from the 2nd line of the 1.9 configuration right at the beginning, because he doesn't knows it.
This would happen continuously with every character he doesn't know until the end of the configuration file. (If I were to fix it one at a time.)

If there are continuous, fast errors in the terminal, then I use the OBEN pkill command and the terminal at the bottom stops immediately. There I can look at the error messages by rolling back then in peace.

@asqwerth

Code: Select all

..
$ conky: Syntax error (/home/tuaz/.conkyrc:2: unexpected symbol near '#') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
..

This is the error I just described due to the use of 1.9
If you took the trouble to start every single Conky from MX17 - CM in the terminal, you would see the same error, because they are all written in 1.9.

Code: Select all

..
conky: [string "..."]:151: [string "converted config"]:138: unexpected symbol near '}'
..

This is an internal error of 1.10 (--> string..), because your configuration file is clumsy
This happens by copying, changing, etc. pp.

You can debug Conky by adding e.g. -DD at the end:

Code: Select all

pkill -xf "conky -c /path/to/conkyrc -DD" &
conky -c ~/path/to/conkyrc -DD &

But there's no use in it here.

[asqwerth]

Male, many thanks for taking the time and effort to help me through this.

However, I think you are still confused about what I'm asking, maybe because I didn't explain well enough.

I am very much aware of this normal error message:

Code: Select all

$ conky: Syntax error (/home/tuaz/.conkyrc:2: unexpected symbol near '#') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.

that pops up whenever conky 1.10 parses and tries to display a conky config file that is written in 1.9 syntax. I run old and new syntax conky configs concurrently in distros that are already using conky 1.10, including MX15, 16 and 17. The error happens all the time for old syntax files but most of the time conky 1.10 is able to run the old syntax files anyway.


My problem is that despite the error message, you managed to get both old and new syntax versions of the grimy wall clock conky to work on your MX17, and I couldn't.

A) New Syntax Config file:

In your post here: viewtopic.php?p=465425#p465425

you converted the old syntax grimy wall clock to new syntax and got it to run.

I tried using your new syntax config file to run on Manjaro and could not.

In my post here: viewtopic.php?p=465609#p465609 , I detailed the error message I got, which has nothing to do with conversion (since the config file was new syntax). It's to do with not having some cairo modules.

I'll have to check out your converted config file on MX17, as I haven't done so after you posted that you got the old syntax config file to work on MX17.


B) Original grimy wall config file - Old Syntax

In your post here: viewtopic.php?p=465619#p465619

you were able to run the original old syntax file in MX17's conky 1.10.

In my post here: viewtopic.php?p=465626#p465626 , I booted back into MX17 and tried to run the original syntax (1.9) grimy wall config file that I downloaded from the deviantart link you provided previously ( viewtopic.php?p=455468#p455468 ).

I also tried to use the pkill command following what I saw from your screenshot here:

http://www.imagebam.com/image/a6362e1023524444 , but I admit I can't recall if I added the "&" at the end.


Below the usual "conversion" error message, I got:

conky: [string "..."]:151: [string "converted config"]:138: unexpected symbol near '}'

[1]+ Exit 1 conky -c "/home/tuaz/.conkyrc"

You have said that:

...This is an internal error of 1.10 (--> string..), because your configuration file is clumsy...

Regardless of whether the original old syntax config file is clumsy, you got it to work. That is why I'm puzzled because it didn't work for me.

I used the original downloaded config file from deviantart; I only adjusted the config file to point to the file path for the lua script, and edited the lua script to insert the path for the images folder. Did you use that same config file or did you redo some parts of it yourself?

... the pkill command is specified above with full path in quotation marks

- below is the start command. If the configuration to be executed is in the user's $HOME, the full path need not be specified. No quotation marks!

Both commands need the AND character & at the end, so that the terminal / process is released again.

Noted.

[male]

@asqwerth
write large on your display:
"Conky1.9 is / was never perfect. It can't be Conky1.10 because it requires the perfect user with LUA knowledge.
(I leave out the mistakes of the users)

It'll ease your confusion a little. Further will diminish if you take the time to read this thread with the following 3-4 pages.
ututo introduces a configuration 1.9 with a Lua script.
The user Dobbie03 wants to execute this configuration (converted) in 1.10 on his computer after initial difficulties...

I think, it clarifies very well your "confusion"
-----------------------------------------------------------------------
To our / your problem: the only difference between your and my configuration is, you have packed the Lua script into the directory LUA...

[asqwerth]

@asqwerth
write large on your display:
"Conky1.9 is / was never perfect. It can't be Conky1.10 because it requires the perfect user with LUA knowledge.
(I leave out the mistakes of the users)

It'll ease your confusion a little. Further will diminish if you take the time to read this thread with the following 3-4 pages.
ututo introduces a configuration 1.9 with a Lua script.
The user Dobbie03 wants to execute this configuration (converted) in 1.10 on his computer after initial difficulties...

I think, it clarifies very well your "confusion"
-----------------------------------------------------------------------
To our / your problem: the only difference between your and my configuration is, you have packed the Lua script into the directory LUA...

Thank you so much for that bunsenlabs forum link. Dobbie03's problems and even his error messages trying to run the clock conky in Arch are so similar to my problems trying to run grimy wall clock in Manjaro!

Now I know there is an issue with lua scripts and/or cairo and/or imlib2 (due to directory structure maybe) running under conky 1.10 in Arch-based systems. That explains why grimy wall clock (new syntax) did not run in Manjaro.

In the end, Dobbie03 never got it running. S11 rewrote the conky for him, he downgraded to conky 1.9, and then the clock conky worked.

https://forums.bunsenlabs.org/viewtopic ... 399#p54399


So anyway, knowing that Manjaro/Arch is just bad for certain conkys with lua stuff, I tried running your new syntax grimy wall clock conky in MX17 and it worked!

But even though you managed it in MX17, the old syntax original version of the clock simply does not work for me in MX17. Really puzzling. I tried using pkill, but the error message is as before: some error in line 151 and 138, then the terminal stops there, no further text, and the conky never appears on my desktop.

I think that's about as good as it's going to get. The new syntax clock works, but I can't manage it through Conky Manager as CM doesn't detect it. So if I want to use it in MX17, I will have to manage it and any other conkies with my own conky startup script and not through CM.

[male]

I'm glad you read that.
Exactly, and PackRat probably has his thumb on it...

Recently, I had a user whose Conky did not gain transparency
Unfortunately, he had already successfully followed another advice, to create a new user.
.............................................................................................................

Since I am not on the right machine now, I will show you my grimy_wall 1.9 today.
Because it interests me already, why this does not want to work with you.

[male]

Here's the 1.9
and please note that the fancyclock.lua script is started from the original directory of the MX installation (!) I didn't move it to ~/LUA

Code: Select all

# conky -c /media/5/conky/grimy_wall/grimy_conkyrc_clock &
# pkill -xf "conky -c /media/5/conky/grimy_wall/grimy_conkyrc_clock" &
# clock
# written by easysid
# Sun, 20 Oct 2013 10:44:04 IST

###  Begin Window Settings  ##################################################
# Create own window instead of using desktop (required in nautilus)
own_window yes
own_window_type normal
own_window_transparent yes
own_window_hints undecorated,below,skip_taskbar,skip_pager   #,sticky
#own_window_colour gray
#own_window_class Conky
#own_window_title easysid Mech Clock

# Use the Xdbe extension? (eliminates flicker)
# It is highly recommended to use own window with this one
# so double buffer won't be so big.
double_buffer yes

### ARGB can be used for real transparency
### NOTE that a composite manager is required for real transparency.
### This option will not work as desired (in most cases) in conjunction with
### own_window_type normal
# own_window_argb_visual yes

### When ARGB visuals are enabled, this use this to modify the alpha value
### Use: own_window_type normal
### Use: own_window_transparent no
### Valid range is 0-255, where 0 is 0% opacity, and 255 is 100% opacity.
# own_window_argb_value 0 #255

#minimum_size 320 320	### w|h
#maximum_width 320		### w
minimum_size 350 260	### w|h
maximum_width 350		### w

gap_x 40	### l|r
gap_y 45	### u|d

# Aligned position on screen: tl, tr, tm, bl, br, bm, ml, mr
alignment bl  #mm #tr
##################################left#################  End Window Settings  ###
###  Font Settings  #########################################################
# Use Xft (anti-aliased font and stuff)
use_xft yes
#xftfont Liberation Sans:size=15
xftfont monofur:bold:size=10

# Alpha of Xft font. Must be a value at or between 1 and 0 ###
xftalpha 1
# Force UTF8? requires XFT ###
override_utf8_locale yes

##############################################################################

uppercase no

######################################################  End Font Settings  ###
###  Color Settings  #########################################################
draw_shades yes #no # amplifies text if yes
default_shade_color 000000

draw_outline no # amplifies text if yes
default_outline_color 000000

#default_color DCDCDC #220 220 220	Gainsboro
#default_color C0C0C0 #192 192 192 Silver
#default_color B0E0E6 #176 224 230 PowderBlue
default_color  778899 #119 136 153	LightSlateGray
color0 8FBC8F #143 188 143	DarkSeaGreen
color1 778899 #119 136 153	LightSlateGray
color2 D8BFD8 #216 191 216	Thistle
color3 9ACD32 #154 205  50	YellowGreen
color4 FFA07A #255 160 122	LightSalmon
color5 FFDEAD #255 222 173	NavajoWhite
color6 00BFFF #  0 191 255	DeepSkyBlue
color7 5F9EA0 # 95 158 160	CadetBlue
color8 BDB76B #189 183 107	DarkKhaki
color9 CD5C5C #205  92  92	IndianRed
#####################################################  End Color Settings  ###
###  Borders Section  ########################################################
draw_borders no
# Stippled borders?
stippled_borders 0
# border margins
border_inner_margin 0
border_outer_margin 0
# border width
border_width 0
# graph borders
draw_graph_borders yes
#default_graph_size 15 40
#####################################################  End Borders Secton  ###
###  Miscellaneous Section  ##################################################
# Boolean value, if true, Conky will be forked to background when started.
background yes

# Adds spaces around certain objects to stop them from moving other things
# around, this only helps if you are using a mono font
# Options: right, left or none
use_spacer none

# Default and Minimum size is 256 - needs more for single commands that
#text_buffer_size 1028 ## only use if required - uses resources

# Subtract (file system) buffers from used memory?
no_buffers yes

# change GiB to G and MiB to M
short_units yes

# Like it says, ot pads the decimals on % values
# doesn't seem to work since v1.7.1
pad_percents 2

#   Maximum size of user text buffer
#  (default is 16384 bytes)
# max_user_text 16384

# Desired output unit of all objects displaying a temperature. Parameters are
# either "fahrenheit" or "celsius". The default unit is degree Celsius.
# temperature_unit Fahrenheit

## Imlib2 image cache size, in bytes. Defaults to 4MiB. Increase this value
## if you use $image lots.		Set to 0 to disable the image cache.
imlib_cache_size 0

#top_name_width 15
##############################################  End Miscellaneous Section  ###
###  LUA Settings  ###########################################################
# lua_load ~/wea_conky/draw_bg.lua
## ${lua conky_draw_bg 10 0 0 0 0 0x000000 0.2}
## ${lua conky_draw_bg corner_radius x_position y_position width height color alpha}
##
# lua_load /media/5/Conky/LUA/draw-bg.lua
# lua_draw_hook_pre draw_bg 50 0 0 0 0 0x000000 0.3


update_interval 1

# -- Lua load -- #
#lua_load /media/5/Conky/easysid/MechClock/fancyclock.lua
lua_load ~/.conky/grimy_wall/fancyclock.lua
lua_draw_hook_pre main

TEXT





${goto 225}   UP:
${goto 225}${uptime_short}
${goto 150}${time %a}
${goto 260}${time %b}
${goto 260}${time %d}



${goto 175}${time %Y}

[mrneilypops]

antix-17.2-sid








neofetch system info
https://github.com/dylanaraps/neofetch
glances system monitor
https://nicolargo.github.io/glances/
mpv media player
https://mpv.io/
rox file manager
http://rox.sourceforge.net/desktop/ROX-Filer

[KoO]

@ mrneilypops Very pleasing & nice layout too.And your wallpaper just tops it off .

[KoO]

Maybe we should just keep the conky stuff in the conky post. Almost three pagers of conky.