Search found 115 matches
- December 23rd, 2019, 11:36 pm
- Forum: Translations & Internationalization
- Topic: Esperanto translation / Esperanta traduko
- Replies: 35
- Views: 21291
Re: Esperanto translation / Esperanta traduko
Saluton, ĉiuj! Mi nune laboras traduki po/wesnoth/eo.po-on. La retpoŝto de Manuel ne funkcias.
- April 1st, 2014, 4:34 pm
- Forum: Release Announcements, Compiling & Installation
- Topic: Wesnoth 1.11.12 (1.12 beta 3)
- Replies: 21
- Views: 14330
Re: Wesnoth 1.11.12 (1.12 beta 3)
Alert to git users: I've just discovered that the name of the wesnoth repository has changed. As far as I can tell, the 1.11.12 tag does not appear in 'wesnoth-old', while, according to Github, it does appear in 'wesnoth'. I'll go clone the new repo now, even though there's probably better ways to f...
- March 9th, 2014, 8:19 am
- Forum: Release Announcements, Compiling & Installation
- Topic: Can’t find the 1.11.10 tag
- Replies: 19
- Views: 6702
Re: Can’t find the 1.11.10 tag
Thanks for the help. This thread does help clear my mind about how branches work.
- March 5th, 2014, 6:15 pm
- Forum: Release Announcements, Compiling & Installation
- Topic: Can’t find the 1.11.10 tag
- Replies: 19
- Views: 6702
Re: Can’t find the 1.11.10 tag
Ok, that makes sense. :eng: But I can't figure out if that relates to the problem I was having. How does the checkout directory effect merges? When I first tried to switch from 1.10.7 to 1.11.10, I did 'git pull origin master', so git should have had the information it needed without looking at the ...
- March 5th, 2014, 5:38 pm
- Forum: Release Announcements, Compiling & Installation
- Topic: Can’t find the 1.11.10 tag
- Replies: 19
- Views: 6702
Re: Can’t find the 1.11.10 tag
Well, if you pull now, you can check out 1.11.10-retag if you want to, but 1.11.10 has a rather important bug, so you should really get 1.11.11 instead. Done. It looks like you had 1.11.10, but hadn't merged FETCH_HEAD into master for some reason. (which is a complicated way of saying, you fetched,...
- March 4th, 2014, 6:25 pm
- Forum: Release Announcements, Compiling & Installation
- Topic: Can’t find the 1.11.10 tag
- Replies: 19
- Views: 6702
Re: Can’t find the 1.11.10 tag
I'm doing this without first pulling for 1.11.11: $ git branch * (no branch) master $ git describe --tags 1.11.10 $ git checkout master Checking out files: 100% (1268/1268), done. Previous HEAD position was ce43713... another pot-update, just to be sure Switched to branch 'master' Your branch is beh...
- February 25th, 2014, 7:32 pm
- Forum: Release Announcements, Compiling & Installation
- Topic: Can’t find the 1.11.10 tag
- Replies: 19
- Views: 6702
Re: Can’t find the 1.11.10 tag
My clone is only about 2 weeks old. (My computer is new.) I used it to install 1.10.7. Per your advice, I used the following commands: git reset --hard 1.10.7 git pull Thankfully, I did get a successful checkout from this, but at the end of the 'git pull' output, I got this message: You are not curr...
- February 25th, 2014, 4:44 pm
- Forum: Release Announcements, Compiling & Installation
- Topic: Can’t find the 1.11.10 tag
- Replies: 19
- Views: 6702
Re: Can’t find the 1.11.10 tag
At the risk of side-tracking the thread, I do blame git for allowing these subtle mistakes that lead to massive frustration. Mercurial is more strict about how its repos are structured, and it doesn't have these problems.
- February 25th, 2014, 7:25 am
- Forum: Release Announcements, Compiling & Installation
- Topic: Can’t find the 1.11.10 tag
- Replies: 19
- Views: 6702
Re: Wesnoth 1.11.10 (1.12 beta 1)
Try git fetch origin 1.11.10 and then git checkout 1.11.10 . $ git fetch origin 1.11.10 From https://github.com/wesnoth/wesnoth-old * tag 1.11.10 -> FETCH_HEAD $ git checkout 1.11.10 error: pathspec '1.11.10' did not match any file(s) known to git. When I did the pull earlier, git tried to do some ...
- February 24th, 2014, 7:21 am
- Forum: Release Announcements, Compiling & Installation
- Topic: Can’t find the 1.11.10 tag
- Replies: 19
- Views: 6702
Can’t find the 1.11.10 tag
I can't seem to find a git tag for this release. I've done 'git pull origin master'. How do I checkout 1.11.10?
Split from here. ― shadowm
Split from here. ― shadowm
- June 19th, 2013, 5:49 pm
- Forum: Lua Labs
- Topic: Event parameters
- Replies: 4
- Views: 2630
Re: Event parameters
Yes, that's noted in the comment.
- June 19th, 2013, 4:20 am
- Forum: Lua Labs
- Topic: Event parameters
- Replies: 4
- Views: 2630
Re: Event parameters
Code: Select all
H = wesnoth.require 'lua/helper.lua'
-- weapon may be either 'weapon' or 'second_weapon'
local length = H.get_child(wesnoth.current.event_context, weapon).number
- March 5th, 2013, 7:06 pm
- Forum: Lua Labs
- Topic: Wesnoth Lua Pack: Development Thread
- Replies: 106
- Views: 61094
Re: Wesnoth Lua Pack: Development Thread
I know Lua well; I know it has first-class functions. I copy pointers to global functions to local variables for efficiency: Local variables are very quick, since they are accessed by index. If possible, make global variables local (weird, eh?). Seriously, it works great and indexed access is alway...
- January 4th, 2013, 8:07 pm
- Forum: Lua Labs
- Topic: vultraz's lua questions
- Replies: 100
- Views: 31083
Re: vultraz's lua questions
This is untested, but I think it's pretty simple once you understand it: -- You need get_variable because you can't iterate over something you get -- through set_wml_var_metatable. wml = wesnoth.get_variable(var_name) for _, tag in ipairs(wml) do wesnoth.wml_actions[tag[1]](tag[2]) end EDIT: Fixed t...
- December 10th, 2012, 7:36 am
- Forum: Lua Labs
- Topic: Dugi's lua questions
- Replies: 70
- Views: 19130
Re: Dugi's lua questions
Try this:
Race is a property of the unit type, not the unit. (I included the __cfg field because the wiki doesn't list race as a field.)
Code: Select all
wesnoth.unit_types[unit.type].__cfg.race