Change default `hg log` template? [closed] - mercurial

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
Is it possible to change the template that hg log uses by default? I would like to derive a such template that would look like the default but would use mailmap function to show commit author instead of the original recorded author.

Yes, you can do that via the [alias] section in an applicable .hgrc file. So if you know how to create an appropriate template, it's easy (I don't know what mailmap output looks like, so this here is just an example how to tackle it in .hgrc):
[alias]
log = log --template="{date|isodate} {author}\n\t{desc|tabindent}\n\n"
The main issue would be where to get the committer info from - a property mercurial doesn't record by default (that is author and committer are the same). Probably there do exist extensions which allow that distinction - do you happen to use one?
Additionally: I would recommend to NOT overwrite a default command output, but to define a new command like
[alias]
mlog = (whatever you need here)

Related

Why does some files miss when committed to Subversion? [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I am developing a website for a company. However some of the css attributes which are in my project goes missing when I commit my code to the subversion repository.
So in the other end when my team mates access it, the attributes goes missing. I reassured that it was not a mistake when I commit. How can I resolve this?
Subversion commits are atomic and consistent. If some files are missing, then they were not included in your commit or were not even added to your working copy with the svn add command.
When you put new files to your working copy, you first need to tell Subversion client to begin tracking them, i.e. add them to the working copy. You need to do this using the svn add command.
Before you commit, you need to examine the status of your working copy with the svn status command. It will help you find out whether there are any unversioned files or irrelevant changes.
Read SVNBook | Basic Work Cycle.

Transform xlsx to CSV [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I need to transform an xlsx file to CSV in AIX. The server doesn't have any command for that and I am not allowed to install anything on it. Also, no Python/Perl library for reading Spreadsheets are installed on the server.
Is there still any work around for doing this?
P.S.: it has to work with what is on the server
xlsx is an open xml format, specifications can be found.
Otherwise libraries for perl can be found on CPAN, sources may help to pick some parts.
To start maybe unzip the .xslx it will give a set of xml files and have a look if data can be retrieved.
It is no way to do it or at least not an easy one (like a simple script or command).
Maybe by working on that xml files (Nahuel Fouilleul answer) but it will take too much time.
jugging by reception alone of the question it looks like people don´t want to touch this issue even with a stick.

Is ./ really needed for pathing? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I'm wondering if the ./ in paths are really needed since,
./myfile.jpg
myfile.jpg
If both targets the current folder. Why are ./ sometimes used and sometimes it isn't used? Are there advantages or bugs it fixed when uploaded to a root server vs sub-domains or other reasons?
./ means the current working directory. You can just reference the file directly by name, without it.
. = This location
.. = Up a directory
It means that ./foo.html is just foo.html. And it is optional, but it may have relevance if a script generated the path (relevance to the script that is, not how the reference works). You can omit it by the way. It’s useful only for clarity. There is no functional difference between it being there and not being there.
You can use the following list as quick reference:
/ = Root directory
. = This location
.. = Up a directory
./ = Current directory
../ = Parent of current directory
../../ = Two directories backwards

Config files for a script [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I have a script in bash in linux that is supposed to import data from csv into mysql database.
I need to make this script as generic as possible so I need to control it using config files that will specify which data goes to which table, etc. so that I don't change the script in the future when I need to make modifications to the tables for example.
How can I start and how can I do it ? as I am completely new to this topic.
When you are completely new, first try make it running without the generic approach. Perhaps you can already set the dynamic fields (that you want to move to a config file later) using variables.
You will have to rewrite the code few times when you are learning scripting and notice where you need common functions or config files.
Once you have a running prototype, copy the solution to a new directory and go on from there. One way would be writing all dynamic variables in config files:
field1="value1"
field2="value2 with spaces, that is why I use quotes"
field3="3"
field4=""
In the main script you can read the config file with source yourfile.cfg.
Perhaps you know which set of variables you want when you start your script.
Then you can use a parameter for it:
#!/bin/bash
if [ $# -eq 0 ]; then
echo "No parameter given, using default"
source default.cfg
else
source $1.cfg
fi

In Mediawiki, where are my changes actually stored [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
When I actually write in the wiki, where are the changes actually being stored?
I have searched the source code for keywords that i have actually written and i cant find it, which obviously means its being stored where it cannot be searched directly.
I have made changes to it i.e. written in it, but sourcetree does not seem to be recognising it.
Do you mean the site's contents? They are stored in a database file which is read and written by the code.
It would be quite unmaintainable, if not outright dangerous, to mix user-submitted data with executable code.
They are stored in a database table called page (or something similar)