I am using neomutt and configure the way the senders name is displayed.
(not altering display name in outgoing mails)
index_format can do that, and it's defeault is
%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s
L means author's name.
I like to control author's name and
want that nickname I've set with alias will be displayed.
Is this possible?
You need to set reverse_alias and define aliases for people You want to display with nickname. This will affect displaying on index only as You want - no changes in pager or anywhere else.
Example:
set reverse_alias = yes
alias boss My boss <my.boss#exmaple.org>
reverse_alias in docs: neomutt, mutt
Related
There is a custom record type configured in NS. It has a name and a free-form text field called full_name. Name is a standard field, full_name is a custom field. There is another record type which has a field of type List/Record with the previous type. On the form this field is present as drop-down. The drop-down show names of records. The goal is to show full names instead of names in the drop-down. Is it possible to mark somehow full_name field so it is available in the drop-down view instead of just name? Any ideas how to achieve this with NS?
Depending on your exact needs, it may make sense to add another custom field to the record containing your drop down. You can source this field from the full_name field on the custom record. This field does not need to store the value if it's only for display purposes.
Add a new field to the record containing the drop down
Set the type to be text
Name it appropriately
Under the 'Sourcing and Filtering' tab, set the source by field to the drop down
A field with type List/Record type can only show standard Name field. However, you can create a custom field dynamically on before record load of a user event script. Check the nlobjForm.addField. Please keep in mind that the value of it will not be saved. Saving the value is another story.
I'm Use civicrm with drupal, and I import data in to contact but my data have some row missing first or last name, and first or last name is compulsory so its not uploaded,
So where is back-end setting for civi where I'm make first or last name optional,
Is that possible?
By default, there are two tests that are run before creating a contact in CiviCRM. You only have to pass ONE of these two tests for the contact to be created.
1) Do they have a first name and a last name
OR
2) Do they have an email.
There is NOT a "back-end setting for civi where [you can] make first or last name optional" but if you have an email address for that contact, it will not be required.
One work around if you need to import contacts that don't have either an email or a first name and last name is to create a dummy email address like 'dummy#example.com' and add this to the data that you are going to import.
This is hacky, but use a spreadsheet to insert "FixThisName" or some findable text and import. You can search and edit in Civi after.
I created articles with alias overview-of-trips but when I try to view the article url become index.php/destinations/2012-08-08-05-05-05/thailand/overview-of-trips it should be
some thing like index.php/destinations/thailand/overview-of-trips
I queried in xma7k_content db table to find this date/time, but I don't know from where it attaches this date/time.
Menu Item Type is : Single Article
You should check your category (destinations) alias it must be date so it is appearing like this.
I want to have a content entry block. When a user types #word or #blah in a field, I want efficiently search that field and add the string right after the "#" to a different field as a n entry in a different table. Like what Twitter does. This would allow a user to sort by that string later.
I believe that I would do this as a part of the save method on the model, but I'm not sure. AND, if the #blah already exists, than the content would belong to that "blah"
Can anyone suggest samples of how to do this? This is a little beyond what I'm able to figure out on my own.
Thanks!
You can use regex (re) during save() or whenever to check if your field text contains #(?P<blah>\w+) , extract your blah and and use it for whatever you want .
Not sure I have the correct terminology here. I'll explain what I want to do and you guys can tell me if it's possible.
I'm using MediaWiki as a Customer List page. So, I have a category for customers, and for instance, I have 20 customers. Inside the actual customer page I have several "headings" that make up the customer page, including an infobox. What I'm wanting to know is, how I would go about "including" the headings as a template "Customer Landing Page". Meaning, each "Customer Landing Page" (Customer A or Customer B, etc, etc) has the same "headings", but not the same content - so all I want is that each customer page, I can include a "template" and it has the same headings with no content under the headings - so that each time I change this "template" file, it changes it on every customer, and all I have to do is edit the content on the customer page that is required.
You'll have to make one big template for the entire customer page, in which you put all the info. I'll make an example template for a page with two headers, "Customer Landing Page" and "More info". The headers are fixed, and the contents below it vary between customer page.
First, you make the template by creating the page Template:Customer
In here you put:
=Customer Landing Page=
{{{landingpagetext}}}
=More info=
{{{moreinfotext}}}
The triple accolades indicate the variables you will later define in each customer page. For customer A:
{{customer
| landingpagetext = This is the landingpage for customer A
| moreinfotext = This customer is a vegetarian
}}
Customer B:
{{customer
| landingpagetext = This is the landingpage for customer B
| moreinfotext = This customer likes Tom & Jerry
}}
The double accolades indicate the start of a template, and the first word is the templatename used. Then after each pipe ( | ) you can assign variables. I only used newlines to make it easier to read, you don't have to do that (but it makes it easier to maintain).
If you don't use the variable names (like {{customer|Landing page text|More info text}} ) you can access the variables by the order they are defined in, using {{{1}}} and {{{2}}} in the template.
If the customer pages are really big you might want to split the template up and use one per section.
Another option (but more complex) is the use of Navboxes. This requires a lot more set up but mayb be closer to what you are looking for?
You could look at using MultiBoilerPlate, I use this to set default text in pages. I would call this a template but Mediawiki uses that term for something else. If you just want to load the same default text when you start a new page and then fill it in with your own text, then I think this is what you need.