mu-msg-fields: Mark contact fields as phrase-enabled

This commit is contained in:
Dirk-Jan C. Binnema 2019-08-01 22:11:39 +03:00
parent a8752e28c3
commit fc0ea805f5
2 changed files with 3 additions and 4 deletions

View File

@ -67,8 +67,6 @@ struct _MuMsgField {
const char _xprefix; /* the Xapian-prefix */
FieldFlags _flags; /* the flags that tells us
* what to do */
};
typedef struct _MuMsgField MuMsgField;
@ -324,7 +322,8 @@ gboolean
mu_msg_field_xapian_index (MuMsgFieldId id)
{
g_return_val_if_fail (mu_msg_field_id_is_valid(id),FALSE);
return mu_msg_field(id)->_flags & FLAG_XAPIAN_INDEX ? TRUE: FALSE;
return mu_msg_field(id)->_flags &
(FLAG_XAPIAN_INDEX | FLAG_XAPIAN_CONTACT) ? TRUE: FALSE;
}
gboolean

View File

@ -192,7 +192,7 @@ gboolean mu_msg_field_is_cacheable (MuMsgFieldId id) G_GNUC_PURE;
/**
* is the field Xapian-indexable? That is, should this field be
* indexed in the in the Xapian database, so we can use the all the
* indexed in the Xapian database, so we can use the all the
* phrasing, stemming etc. magic
*
* @param id a MuMsgFieldId